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!


The design logic behind of unmanaged/self-managed users taken as External users

Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 30, 2023

Hi guys,


When I firstly see the external users under Security top menu, I guess this is for users not in this organization. In my case, I haven't verifed my company's domain or claim its accounts. So the employees in my company as taken as external users too, which seems not so good.

After thinking, I can understand that Atlassian suggests that every company firstly verify the company domain and claim its email accounts. Through doing this, the company can distinguish internal employess (managed accounts) and other external users.

Then, what if the company doesn't have any domain? My employees are taken as external users.

Let's discuss it if you're interested to this topic.



1 comment


Log in or Sign up to comment

I'd like to start by adding some context to the User Management process for Atlassian Cloud Products. When a person creates an account with any email address to use any of the Atlassian Products, this account is created in Atlassian's Identity Provider (IdP). Due to GDPR regulations, any account created in the Atlassian IdP belongs to the end user so that they can change their password, name, and other information they might want to share with the world.

Now, when a company wants to be able to manage their employees account, this causes some issues as the management level of user accounts is very limited by default. Here is where the account claiming comes into place.

Claiming accounts is telling Atlassian that certain accounts in their IdP belong to the company. However, a company needs to verify in some way that the accounts are theirs. That's where the domain ownership claim comes into place.

Let's say that ACME Co. is. a company and as any reputable company, they register the domain This registration will be configured in a DNS and email addresses will follow the pattern, or something similar. When the company goes through the process of claiming domain ownership with Atlassian, is telling them that any accounts are owned by them.

After the domain ownership is completed, ACME Co. can proceed to claim all the accounts and this process will allow the company to have more account management features, such as password complexity, MFA, etc.

This is the recommended approach in all cases, if managing employees accounts is important for the company.

Like # people like this
AUG Leaders

Atlassian Community Events