Managing non SSO/SAML accounts

[Louie Garofalo]

Our organization invites third parties (contractors etc..) to view or sometimes update parts of confluence and jira.

If we turn on Single Sign On via SAML, will that affect accounts with e-mail addresses that use domains we do not manage? Hoping it doesn't affect their accounts at all.

[Dimitris Damaskos · Accepted solution]

I was reading the Documentation of Atlassian about this matter and I see in the article Organization administration on Verify a Domain it states:

When you verify a domain, all the Atlassian accounts that use email addresses with the verified domain become managed by your organization. 

And on the article SAML single sign-on on the Frequently Asked Questions it states:

Can I get SAML single sign-on for domains that I cannot verify?

No. To keep applications and resources secure, you can only use SAML single sign-on with domains you can verify that you own.  

So all the accounts that are do not use email addresses with your verified domain will not be manageable by you and will not be affected. 

[Louie Garofalo]

Thanks, Dimitris!

That makes sense.