You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We currently have a few Atlassian products we are subscribed to. Jira Software Standard is one of them. We would like to add Atlassian Access to our account to provide SSO for all the users part of our organization. However, we also deal with consulting companies for which we would like to provide them some access. These accounts won't belong to our organization and SSO won't be possible for them.
This is why I'd like to understand if I will still have the ability to manually create accounts once SSO is enabled?
Atlassian Access allows you to manage the user account object - and this is done on a domain by domain basis. Within your product (company123.atlassian.com), you can still add users from any domain.
eg: you're company123.com and you have a customer companyABC.com
If you setup company123.com in Atlassian Access to provide SSO, in your Jira instance (company123.atlassian.com), you can invite users from @company123.com and @companyABC.com - your employees will be SSO'd in, but users from @company123.com will use their standard id.atlassian.com accounts to authenticate - UNLESS that company happens to have setup Atlassian Access on their side to protect all of their users.