Make Atlassian's global account model work for you
Atlassian has a global account model that makes it easy for people to access apps, community resources, and support in the Atlassian ecosystem. It also allows people to log in with one account to multiple apps like they can with a Google or Apple account.
The global account model allows an organization admin to administer security and provision users to apps in an Atlassian organization.
What is an Atlassian account?
An Atlassian account is a unique digital identity that a person uses to access and authenticate into the Atlassian ecosystem of apps and services. The account includes attributes like email address and display name. What is an Atlassian account?
What can a user do with an Atlassian account?
An Atlassian account exists independently of the Atlassian apps a person has access to. An Atlassian account allows a user access to multiple organizations, apps, and services with one set of credentials. The user’s profile settings appear consistently across all Atlassian organizations, apps, and services.
How does an account at Atlassian differ in the Data Center versus in the cloud?
With Data Center, you manage your own infrastructure and user accounts are local. With Atlassian cloud, we manage your infrastructure and user accounts are global.
Local model in Data Center | Global model in the cloud |
|---|---|
You create the different accounts for each app. Users are able to log in to each app individually, or you can enable single sign-on so they can log in from one place. | You give access to one global Atlassian account across multiple organizations and apps. Users can log in to multiple organizations and apps with the same Atlassian account. |
What are Atlassian’s identity types?
There are several identity types in the Atlassian ecosystem:
Managed accounts
External users
Portal-only customers (Jira Service Management only)
Identity type | Description |
|---|---|
Managed accounts | These are Atlassian accounts. This account type typically includes accounts that belong to your company’s domain. |
External users | These are Atlassian accounts. This account type typically includes users that don’t have an email address with a company domain but that still need to collaborate within your company. |
Portal-only customers | These accounts are not Atlassian accounts. They only apply to Jira Service Management and not other Atlassian apps. This account type is for people outside your company who seek help related to the use of your company’s products or services. Manage accounts for portal-only customers |
An Atlassian account has these identity types in the context of an organization. This means that someone can be an external user to one organization and a managed account to another organization.
Difference between managed accounts and external users
An organization needs to prove ownership of a domain in order to claim accounts to manage. A managed account belongs to a verified domain and has been claimed by an organization. An external user either doesn’t belong to a verified domain or does, but hasn’t been claimed by the organization.
Example: Acme
Account | Has Acme verified this domain? | Has Acme claimed this account? | Account type |
|---|---|---|---|
User with a company email address: | Yes | Yes | Managed account |
User with a company email address: | Yes | No | External user |
User with a personal email address: | No | No | External user |
Control security and manage users for identity types
Each identity type gives you different security and user management controls as an organization admin.
| Managed accounts | External users | Portal-only customers |
|---|---|---|---|
Manage account details and security settings | You can change account details and enforce security settings. | You can’t change account details, but you can enforce external user security. | You can’t change account details, but you can enforce security settings. |
Ways to require users to authenticate | You can enforce single sign-on, two-step verification, third party log-in options, or password strength with authentication policies. | You can control external user access to data in your organization with external user security. | You can enforce single sign-on and password strength with authentication policies. |
Provision users | Set up your identity provider to sync users and groups. You can manage them from your external directory before syncing updates. Understand user provisioning | Set up your identity provider to sync users and groups. You can manage them from your external directory before syncing updates. Understand user provisioning | Users can sign up for portal-only accounts or Jira Service Management agents can create them. Add a customer to a service project |
Was this helpful?