Administer Atlassian accounts

Until recently, all Atlassian accounts existed as personal accounts, which are accounts that individual users manage themselves. As an administrator, you control the access to products for your users, but you don't have any control over their accounts.

If verify your organization's domain, your users' accounts become managed accounts. As an administrator, you have more control over their accounts and are now able to enforce an authentication policy.

Alternatively, another site can manage your users' accounts, giving administrators of that site control over those managed accounts. In that case, you can no longer enforce an authentication policy on those accounts.

This page

Here's more details about what you do and don't have control over your users' accounts.

Administrator action Personal (or managed by another site) Managed
  Administrator Account holder Administrator Account holder
Change email (error) (tick)

(tick)

(error)
Change name (error) (tick) (tick) (tick)
Change profile picture (error) (tick) (error) (tick)
Delete account (error) (tick) (tick) (error)
Enforce an authentication policy (error) N/A (tick) N/A
  Let's take a look at managed and personal accounts for Teams in Space

Refer to Administer Atlassian accounts for more background on the Cloud sites of Teams in Space.

Teams in Space has two sites and gives access to their own managed users and a few contractors:

You are the site1 administrator, have verified the teamsinspace.com domain, and configured a password policy on site1.teamsinspace.com for users with the @teamsinspace.com email addresses, which means:

Administer personal accounts

As shown in the table above, you don't have much control over accounts that are personal or managed by another site.

Reset a user's password

From the user's profile page under User management, click Reset password. The user receives the email we send out when they forget their password. From there, the user can create a new password. However, the user isn't required to create a new password. The user can ignore the email and continue to log in with their current password.

If your users don't yet have Atlassian accounts

  1. Go to 
     >  User management
    .
  2. Select the user by clicking their name.
  3. Choose Change password.
  4. Enter their new password and choose Change password.

Remove users from your site

Refer to Deactivate or delete users for details about how to remove users from your site:

  • Deactivate a user if you want to manage their account details, but you don't want them to log in to your Atlassian Cloud site.
  • Delete a user if you don't want them to appear on your site at all. Deleting a user doesn't impact the Atlassian account itself. It only disassociates the Atlassian account from your site.

Gain more control over your users' accounts

If you want to do more to administer these user accounts, here are some options:

  • If you own the domain they're on, claim the domain.
  • If you don't own the domain, invite the same users to your site with email addresses for a domain you do own. At the same time, remove access to your site from their original account. Any content they created while logged in with the original account will still exist, but the user won't appear as its creator.

Administer managed accounts

As an administrator of managed accounts, you have more control over your users' account details. The biggest advantage to administering managed accounts is that you can associate them with your organization's domain and apply authentication policies across your organization. Authentication policies allow you to enforce security requirements for how your users log in. Atlassian Cloud's existing policies include password requirements and SAML, but we have future plans to support two-step verification.

To make your users' accounts managed, their account email addresses must be on a domain you or your organization owns and can verify. Refer to Domain verification for details on how to verify your domain.

If an Atlassian account user doesn't have access to your site but has an email address with the domain you claimed

Add the user to your site with no access to any products. From there, you can edit their details, but the user won't count towards your monthly bill.

Update a user's full name, username, or email address

Refer to Edit users for details about how to update a user's full name, username, or email address. After you change a user's email address, we'll send your user an email asking them to verify their email address to access their account.

When you make any of these changes, we'll reflect them at all other sites the account can access. For example, if you change an account's full name at site A, and that same Atlassian account is a member of sites B, C, and D, all of those other sites will reflect the full name change.

Reset a managed account's password

  • To reset an individual user's password—From the user's profile page under User management, click Reset password.
  • To reset all your users' passwords—From the Password Policy page under Authentication, click Reset passwords now.

Your users current passwords immediately become invalid, and we'll log them out of their current sessions. We'll notify your users to set a new password before logging back in.

Remove users from your site

Refer to Deactivate or delete users for details about how to remove users from your site:

  • Deactivate a user if you want to manage their account details, but you don't want them to log in to your Atlassian Cloud site.
  • Delete a user if you don't want them to appear on your site at all. Deleting a user doesn't impact the Atlassian account itself. It only disassociates the Atlassian account from your site.

Future improvements may allow an administrator to close individual Atlassian accounts, locking the user's account within the managed domain out of all Atlassian products and sites. In this case, we would require email verification to reopen a closed account.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport