SAML configuration issue causing new accounts to be created instead of logging into the intended account.

Struggling with a SAML issue. We seem to be configured correctly but when I logged in it created a brand new account rather than tieing to the user/org/project that we were configuring it for.. What did we do wrong?

Hey User! To double check, are you on an enterprise level plan?

We are on the Business plan.

Happy to share any info that might have a bearing on this.

Got it! Just checking that it wasn't a plan-level error. Is this happening when logging into a Studio or into sanity.io/manage ?

Well we ask our iDP to push us through. There isn't a login url specified. I would expect to land in manage -- I think folks can pivot to studio from there can't they? (Total Noob alert)

I updated the Login URL to /manage but it still logs me into the "fake" account not the "real" account

Does the fake account have the same login information as the real account but use a different provider?

So they both have the same email address firstname and lastname. The "fake" account was created on the fly the first time I tried to login using SAML.

We only have one SAML provider...

Can you share your SAML set up? You can DM me if you're like to keep it private.

Woops I was away this morning.Sure -- Thanks! I'lldo that now.

Just checking in this morning. Anyone have any ideas?

Thank you for being so patient as we worked to find a solution for you. This is not an issue with your SAML configuration after all. This is the intended behavior when using a new authentication provider to log into the Studio (even if it's using the same email address and information). There's no way to configure SAML to work around this.

So how do I get SAML to log folks into our actual corporate account?

Like with other new user accounts, you need to invite the account to the project. The invitee would then need to log in with SAML and accept that invite. You can then delete the old account.

Sooo. That seems to be the case also forMY account how does that "owner/Admin" permission get tranferred?This is most odd...

So we find that there is no way to do that either until the intended user has Deleted their original account. That is not going to work is it?Why isn't there a way to connect to the existing account or choose auth methods as the admin?

-- Sorry if I am getting a little whiny.