Update (24th May 2024): this change has now been released to all customers.
Hi everyone,
We’re excited to share that soon admins like yourself will be able to verify the same domain across multiple Atlassian organizations. If you come from a company with a decentralized structure – e.g. separate business units or subsidiaries – you can have the same domain verified in separate Atlassian organizations. This gives you the autonomy and flexibility to manage your organization and accounts without affecting another organization.
When you verify a domain, you can claim specific accounts from that domain in your organization. When you claim these accounts, you gain:
More control over Atlassian accounts – you can edit, delete, or deactivate their accounts.
The ability to customize and enforce security policies on your subset of accounts if you have Atlassian Guard (previously Atlassian Access) – you can enforce 2FA (two-factor authentication) or set up SSO (single sign-on) so that your identity provider’s policies apply to your managed accounts.
You can only manage an Atlassian account in one organization. If someone else manages an account in another organization, you’re unable to claim the account.
For example: Employees of Acme US and Acme UK both share the acme.com domain. There are a total of 1,000 Atlassian accounts belonging to the acme.com domain. After verifying the domain, Acme US can claim 400 of the accounts, and Acme UK can claim the remaining 600 accounts. Because alana@acme.com is already managed by the Acme US org, her account cannot be claimed by Acme UK.
This update does not change how people collaborate so you can still invite users to collaborate with your team, even if you do not manage their account.
We anticipate to start rolling this change out later this month.
If you have any feedback or questions about these changes, leave a comment and I’ll be in touch!
Cheers,
Aneita Yang
Atlassian Access Product Manager
Aneita
Senior Product Manager, Atlassian Access
7 accepted answers
13 comments