Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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: 

  • subsidary1.atlassain.net
  • subsidary2.atlassian.net

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

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
TAGS
Community showcase
Published in Atlassian Access

What's new in Atlassian Access - Webinar

Based on your valuable feedback, we have released several new features to help you gain administrative flexibility with authentication policies, visibility into shadow IT with automatic product disco...

99 views 2 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you