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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Multiple Orgs, Same SSO Provider

I'm wondering if there is a "best practice" for setting up organizations in Atlassian Access. Our scenario is our parent company provides Okta to subsidiaries. A shared IT team provides all IT support for the subsidiaries, including support of Atlassian products. For various reasons, our parent company wants to keep walls between the data and resources of subsidiaries. 

Ideally we'd have two different Jira/Confluence instances, one is new the other would be migrated from an existing Jira server: 


Where each would be unique Okta Applications. In Okta we can transform usernames (email addresses) based on the application. 

For Atlassian Access, should we have multiple separate subscriptions for Atlassian Access or would they be lumped under multiple organizations under Atlassian Access? 

1 answer

0 votes
Ed Letifov _TechTime - New Zealand_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 08, 2020

It's a pyramid (top to bottom): A single org admin user in Atlassian Access may create and have access to multiple organisations. I do believe billing will be per organisation (as it is based on the number of managed users). An organisation in Access may have multiple domains "claimed". A user is attributed to an organisation (as a managed user) based on their email domain. 

When the user shows up at Atlassian's login page, everyone has to enter their email – this is when the decision is taken to proceed with asking for a password or redirect to the IdP (Okta).Your connection to Okta will be set up per organisation.

If your subsidiaries have the same email domain – you can only have a single organisation in Access, and thus only one Access bill/subscription and by extension a single Okta application.

If your subsidiaries have different email domains – you can have different organisations (and thus different bills/subscriptions/Okta applications).

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events