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

Claiming a domain, impact of users outside the Access organization

Hi Community,


For my customer I’m analyzing the impact of Atlassian Access subscription.

Within the company (all using the same domains) they currently have multiple Atlassian organizations. For one of these organizations the plan is to use Atlassian Access for SSO.

What will be the impact of installing Atlassian Access for Atlassian organization A on the other Atlassian organizations who use the same emailadresses (domain)?

  • The amount of users Access will be billed for are these counted only the ones within organization A or all the Atlassian users in the company (within these multiple organizations?).
  • Will the Atlassian users in the other organizations be impacted while claiming the domain in org.A and forcing SSO in org. A?


Thanks a lot!

1 answer

1 accepted

1 vote
Answer accepted

Hi @Tom Braat 

I can list down a few points:

  1. Once you claim the domain, no one else can claim the same domain. 
  2. Once a domain is claimed all the users with the domain are counted and used as managed users from the claimed domain organization.
  3. Installing/Enabling Atlassian Access will not impact other organizations until to start using Atlassian access features like SSO & enforcing SSO.
  4. All users with the claimed domain and consuming any of the Atlassian cloud products are counted against the Atlassian access bill. To prevent unnecessary billing of all users to your organization you may make use of the non-billable policy feature. Refer: What-is-a-non-billable-policy  
  5. Enforcing SSO is done using authentication policies, you can define who all users should be part of the policy. However, if a user is common to multiple organizations then an organization with Atlassian access and ownership of the domain takes priority and the user would need to log in using SSO. Thus, if you enforce SSO on a user account owned by you, the user has to log in to any of the Atlassian cloud sites using the authentication policies enforced by your organization which claims the account. 


Thanks Utkarsh!


Regarding point 2/3 if the users with the same domain are outside the Atlassian Organization in which Access is enabled, they will also get counted for the access bill? So it doesn't matter how many Atlassian Organizations you have, if users are in the domain they are accounted for the Access bill?

Yes, that is correct. Once you claim a domain, you become the owner of the domain and all the users in the Atlassian cloud using the claimed domain no matter the organization they are part of.

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events