nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Claiming a domain, impact of users outside the Access organization

Tom Braat

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!

Accepted answers

Utkarsh Agarwal

Hi @Tom Braat

I can list down a few points:

Once you claim the domain, no one else can claim the same domain.
Once a domain is claimed all the users with the domain are counted and used as managed users from the claimed domain organization.
Installing/Enabling Atlassian Access will not impact other organizations until to start using Atlassian access features like SSO & enforcing SSO.
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
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.

Regards
Utkarsh

All comments

Utkarsh Agarwal

Hi @Tom Braat

I can list down a few points:

Once you claim the domain, no one else can claim the same domain.
Once a domain is claimed all the users with the domain are counted and used as managed users from the claimed domain organization.
Installing/Enabling Atlassian Access will not impact other organizations until to start using Atlassian access features like SSO & enforcing SSO.
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
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.

Regards
Utkarsh

Tom Braat

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?

Utkarsh Agarwal

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

atlassian-guard

identity-manager