Introducing Atlassian account

Redirection notice

This page will redirect to /display/Cloud/Atlassian+account+for+administrators .

An Atlassian account allows you to use one set of login details to log in to any of your Atlassian Cloud products. 

The integration of Atlassian account with Atlassian Cloud is underway and we are progressively moving a large number of eligible Atlassian customers to an Atlassian account.

On this page

Answers to top questions

Who does this upgrade impact?

This upgrade impacts all Atlassian Cloud customers. If you host our products on your own server, this upgrade will not impact you. 

If you are having trouble with your Atlassian account, contact your administrator or log a ticket at Atlassian support

What do my users see when they upgrade?

Your users follow a simple upgrade process, like the one shown in the following example that shows an existing user being upgraded to an Atlassian account.

Note: The upgrade screens might differ depending on your user's situation and the products they use. 

How do my users log in with their existing credentials?

Atlassian account is like a single sign on service for Atlassian Cloud services. After your existing users have upgraded to an Atlassian account, and the Atlassian account integration is complete for all your Cloud services, they can log in using their Atlassian account credentials across products.

How does this impact REST APIs?

If you are using any REST APIs, they will continue working as per normal. The Atlassian account upgrade will not impact these APIs.

How does this upgrade impact BOT accounts?

BOT accounts using basic authentication to access our products will continue to work only if the BOT account is associated with a single product's instance. If the same BOT account accesses multiple sites in different instances, then you may need to make the BOT account unique or create a new verifiable email address for your BOT account.

This is a temporary workaround until we introduce app-specific passwords, which will allow BOT accounts to access your site securely without verifying the email address.

What happens if we use multiple Atlassian Cloud products?

Atlassian account upgrades are being implemented progressively. If you have multiple Cloud products, such as JIRA, HipChat, and Bitbucket, your users will be upgraded for one product at a time, for example, HipChat users first. In the interim, your users can log in to Bitbucket and JIRA as they do today. If your users use the same email address to log in to all these products, then, when the implementation is complete, their accounts will merge into one Atlassian account, allowing them to log in to all the three products with one account.

What happens if we use a combination of Atlassian Cloud and Server products?

If you use a combination of our Cloud and Server products, for example you host Confluence on your own server, but use cloud-hosted JIRA, Bitbucket and HipChat, this upgrade will only impact your JIRA, Bitbucket and HipChat users. You can continue using the server-hosted Confluence as usual. 

Sign in and security

I've lost my Atlassian account password. How do I retrieve it?

To reset your password, visit the Password Reset page. All you'll need is your email address.


I have not received my verification or forgot password email. Now what?

When you create a new Atlassian account or we upgrade yours, we might ask you to verify your email address. If you do not receive the verification email, check your spam folder for an email from or You can have the email resent from the page that you see when you try to log in.

Can I have more than one Atlassian account?

Yes, you can have multiple Atlassian accounts. However, ensure that you the correct account while logging in to your Atlassian cloud services.

Can I combine multiple Atlassian accounts?

No, it is not possible to combine multiple Atlassian accounts.

Who do I contact if I’m having login issues or there is a problem with my account?

Check our support page or contact us through our website.

Single sign-on integrations

I have password sync set up through an integration between my identity provider (like Okta) and my cloud product. How will this interact with Atlassian accounts?

When your organization is upgraded to Atlassian account, your users will go through a short email verification process the next time they log in. Your integration will continue to work with no problems after the upgrade, and will sync the password provided via your integration with your Atlassian account.

Will my users be asked to change their passwords when they are upgraded to Atlassian account?

Your users will not be asked to change their passwords during this process.

What happens if I have password sync set up through an integration, and my users change their Atlassian account password?

Passwords synced through integrations are pushed to your users' Atlassian accounts. If a user changes their Atlassian account password, they should use that password to log in to their Atlassian account until the next time your integration pushes a password change to Atlassian account.

Account information

Can I change the email address of my Atlassian account?

Yes, you can change the email address for your Atlassian account at

Can I close my Atlassian account?

You cannot close your Atlassian account yourself. You must log a ticket Atlassian support.

I have multiple accounts on with the same email address. How do I make sure the right one is linked to my Atlassian account?

Some Atlassian services (for example and previously allowed for the creation of multiple accounts with the same email address. Only one of these accounts can be linked to your Atlassian account.

To link your desired support account to your Atlassian account, perform the following steps:

  1. Log in to your Atlassian account.
  2. Navigate to your Atlassian account profile page.
  3. In the left pane, click Services.
  4. Locate Atlassian support and click Change account.
  5. In the dialog box that appears, enter the email address with which you created multiple accounts and click Change Connection.
  6. Confirm the change through the verification email we send to the email address you entered to complete the linking process.

It might take a minute or so for the change to take effect.

Atlassian account rollout summary

This will give you a general idea where we are with making Atlassian Accounts available in our Atlassian Cloud products.

Read more about the Atlassian account rollout status.

Atlassian account features

One account COMPLETE

Gone are the days of having multiple accounts for your Atlassian products. Atlassian account will be your one account for everything Atlassian. You'll not only have the one account, but if you're using the web, you'll be logged in everywhere with a shared session. 

More access COMPLETE

Your account gives you instant access to an array of Atlassian services, including Support:

Domain verification COMPLETE

Verify your domain to manage your user's Atlassian accounts. Managing Atlassian accounts allows administrators to change their details and apply authentication policies like password policy or SAML. 

Get in-depth information, and see how to verify your domain at Managed accounts and domain claim verification

Password policy COMPLETE

Applying password policy for Atlassian accounts will be as simple as it is to apply today. You can ensure your managed accounts have a particular password strength, and that they reset it after a specified time period. 

Google sync IN PROGRESS

Easily provision Atlassian accounts for selected Google Apps groups into JIRA and Confluence. They'll be able to login with their Google credentials, and we'll keep their details up to date with a regular sync.


Delegate the authentication of Atlassian accounts you manage to your IdP with SAML. We'll provide support for custom SAML configurations, and popular IdP's, adding new IdP's over time. 

Two Factor Authentication (2FA) PLANNED

Atlassian accounts can enrol in 2FA to increase their security. Administrators of managed Atlassian accounts can also apply a policy enforcing enrolment in 2FA. 

Last modified on Feb 14, 2017

Was this helpful?

Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.