Skip to main content
Answer

Issues Inviting users

  • December 19, 2023
  • 4 replies
  • 152 views

Forum|alt.badge.img+1

We recently enabled SSO via Okta for our company. After doing so, we attempted to invite a new user and received a very strange error:

Unable to login with SAML. Please request an invitation to your SAML Configured team.

 

All of our previous users can sign in via okta with out any issue. There is no way to specify the user is SAML or not when inviting, and we only have SAML auth enabled currently. Has anyone else encountered this? 

Best answer by Eric R

Thanks for following up, happy to hear that this got resolved! This indeed should work with the user accepting the team invitation and it is difficult to determine what exactly caused the issue in this case. Should you run into this issue again, please don’t hesitate to submit a support ticket via this form so we can help identify what may be causing this. Thanks!

Comments

Eric R
Forum|alt.badge.img+7
  • Lucid support team
  • December 20, 2023

Hi there, thanks for your post! This error typically appears when the user in question is on a free account and is not part of your organisation’s Lucid account. Please follow the instructions in our User Management Help Center article to invite the user to the account. Once they have accepted the invitation and appear in your user list, they should be able to log in with Okta. 

 

Hope this helps 😊!


Forum|alt.badge.img+1
  • Author
  • December 20, 2023

The user actually gets this message after we send the invite. They click the link in their email, hit the sign on page and receive the error.


Forum|alt.badge.img+1
  • Author
  • December 20, 2023

Apparently the conflict was due to the user having a previously managed free account - CSM had to manually add him to our account for us to get him in. I feel like there should be a better way to handle this. 


Eric R
Forum|alt.badge.img+7
  • Lucid support team
  • Answer
  • December 29, 2023

Thanks for following up, happy to hear that this got resolved! This indeed should work with the user accepting the team invitation and it is difficult to determine what exactly caused the issue in this case. Should you run into this issue again, please don’t hesitate to submit a support ticket via this form so we can help identify what may be causing this. Thanks!