Hey, couldn't find a definite answer in the docs so I'm asking here. Should the user invite mechanism work expectedly for tenants running SAML SSO exclusively without SCIM?

Let me check @Omri Tcherner

yes the user will be converted to be an SSO user if he is created in the invite with the same loginid/email and tenant

Another question on that @Reuven Zabirov, we want to be able to send the email ourselves and not through Descope's invitation system. Do we and can we generate the invitation URL ourselves through the Go SDK? Does the user need to login through the invitation link directly in order to allow proper migration of the invited user into an SSO user or can it just be through our generic app URL?

You can use the go sdks generate embedded link

GenerateEmbeddedLinkSignUp

that will guarantee the user is created in Descope, thus having the user created, making sure that he merging will work with SSO

Amazing, and just out of curiosity, if the user logs in regularly from the app after being invited, it isn't guaranteed there won't be two duplicate emails with the same user yes?

we toggle him from invited to active when he logs in through your app. you just need to make sure your sign in flow uses sign in or sign up or in actions rather than just sign up.

perfect, so the invite url is not necessary then if I understand correctly. we will still send it, but it shouldn't matter if the user directly logs in through the app then

that's right