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?
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).
Hi Community! Thank you to all who joined our ongoing monthly Atlassian Access demo! We have an engaging group of attendees who asked many great questions. I’ll share a recap of frequently ask...