Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Question on migration to SAML SSO

How does the account creation work when migrating from Atlassian hosted accounts to SSO in the cloud? Do we have to re-create access and permissions for everyone migrated over to SSO or will Atlassian match email addresses in the SAML claim to accounts already created? 

1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 16, 2018

Once you configured the SAML configuration, Atlassian Access would match the Atlassian Account's email addresses that are associated with the verified domain with the email addresses of the account in your IdP.

If they are matched, the user will be able to login via SAML SSO.

Atlassian Access doesn't affect the application access but only Atlassian Accounts. Setting up an Atlassian Access SAML configuration would not create a user in your instance. Think Atlassian Access as a centralized platform to manage users across all Atlassian product. 

So you would still need to create a user in your instance if the user doesn't exist in the instance. But as long the user is created with an email address matches with the IdP's account, the user would be able to login via SAML SSO.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events