Summary

If you want to transfer your apps from an organization that has the centralized user management experience enabled to an organization that uses the original user management experience, you'll see a warning on the Settings  page for the organization that the "Transfer all apps to another organization you administer" option is unavailable for your organization.

Solution

Changing the user management experience for an organization can only be done by contacting Atlassian Support. That being said, there are a variety of requirements that an organization must meet before Atlassian can disable the centralized user management experience:

1. The organization can't be linked to a Trello Enterprise
2. The organization can't be linked to any Bitbucket workspaces
3. The organization can only have a single site, including sandboxes
4. The organization can't have a "site-admins" group that can be deleted
5. The organization can't have any "trusted-users" groups
6. The organization can't have any users who are assigned one or more roles that are exclusive to the centralized user management experience

By following the steps in each section below, you can prepare your organization to have Atlassian disable the centralized user management experience.

Ensure that the organization isn't linked to a Trello Enterprise

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Apps (Apps > Atlassian apps).

3. Search for "Trello."

   • If there are no results for Trello instances in the organization, then no action is required. Skip to the next section.

4. If one or more Trello instances are returned, you will need to contact Atlassian Support to unlink the Trello Enterprise from its current organization and re-link it with a different organization.

Ensure that the organization isn’t linked to any Bitbucket workspaces

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Apps (Apps > Atlassian apps).

3. Search for Bitbucket.

   • If there are no results for Bitbucket instances in the organization, then no action is required. Skip to the next section.

4. For each Bitbucket workspace in the results:

   1. Review the Actions column (select •••) to determine whether the "Manage app" option is present:

      • If not, you can contact Atlassian Support for assistance with unlinking the Bitbucket workspace from the Atlassian organization.

      • If so, the Bitbucket workspace must be permanently deleted before Atlassian can disable the centralized user management experience:

        1. If you wish to preserve any of the repositories from the Bitbucket workspace prior to its deletion, you’ll need to either transfer ownership of those repositories to a different Bitbucket workspace that’s linked to a different organization or clone them to your local machine.

           • For instructions, please see Transfer repository ownership and Clone a Git repository.

        2. Once you are ready to proceed with the deletion of the Bitbucket workspace, you can follow the instructions in Delete a Bitbucket Cloud workspace.

Ensure that the organization only has a single site

Atlassian can only disable the centralized user management experience for organizations with 0-1 sites. Before we can proceed, all additional sites—including sandboxes—must be permanently deleted.

• In order to delete a production site, you must cancel the subscriptions for all apps on the site and wait for the data retention period(s) to expire.

  • For instructions, please see Cancel a subscription.

• In order to delete a sandbox site, you must mark the sandbox site for deletion and wait for the 30-day “offline” data retention period to expire. Before deletion, you can create a backup to preserve your data and configurations, though please note that some data and settings may not be fully recoverable when the sandbox is recreated. For details on what data can be restored.

  • For instructions, please see Delete a sandbox.

Ensure that the organization doesn’t have a site-admins group that can be deleted

Atlassian can only disable the centralized user management experience for organizations that either don’t have a site-admins group or whose site-admins group can’t be deleted.

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Directory > Groups.

3. Search for "site-admins."

   • If there are no results for a group named site-admins, then no action is required. Skip to the next section.

4. Select the site-admins group from the results to view its details.

5. Select ••• > Delete group.

Ensure that the organization doesn’t have any trusted-users groups

To avoid potential conflicts with the now-deprecated trusted users role, an organization can’t have any groups whose names start with trusted-users when disabling the centralized user management experience.

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Directory > Groups.

3. Search for "trusted-users."

   • If there are no results for a group whose name starts with trusted-users, then no action is required. Skip to the next section.

4. For each group whose name starts with trusted-users:

   1. Select the group to view its details

   2. Either:

      • Select ••• > Delete group.

      • Select ••• > Edit group name, enter a new name for the group, then select Save changes.

Ensure that the organization doesn’t have any users with roles that are exclusive to the centralized user management experience

There are a few roles that only exists in the centralized user management experience, or are implemented differently between the original and centralized user management experiences. As such, these roles must be removed from all users before Atlassian can disable the centralized user management experience for an organization.

The affected roles include:

• User access admin

• Site admin

• Basic user role for Compass

• Stakeholder role for Jira Service Management

• Contributor role for Jira Product Discovery

User access admin

For more information on the user access admin role, please see What are the different types of admin roles ? | Roles.

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Directory > Users.

3. Select the Role drop-down and check the box for User access admin.

   • If there are no results for users with the user access admin role, then no action is required. Skip to the next section.

4. For each user returned matching the Role filter for User access admin:

   1. Select the user’s name, email, or avatar to view their details.

   2. In the App access section, select each Roles drop-down and un-check User access admin.

For more information, please see Remove admin permissions from users | Centralized user management content.

Site admin

For more information on the differences between the site admin roles in the original and centralized user management experiences, please see Site Administrator role in the Centralized user management and Original user management experiences.

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Directory > Users.

3. Select the Role drop-down and check the box for Site admin.

   • If there are no results for users with the site admin role, then no action is required. Skip to the next section.

4. For each user returned matching the Role filter for Site admin:

   1. Select the user’s name, email, or avatar to view their details.

   2. If you see a banner indicating that the user is an organization admin:

      1. Select ••• > Remove org admin role.

      2. Review the prompt and select Remove role to confirm.

   3. In the Site administration section, select each Roles drop-down and un-check Site admin.

   4. Optionally, grant the user the organization admin role again by selecting ••• > Assign org admin role, reviewing the prompt, then selecting Assign role to confirm.

For more information, please see Remove admin permissions from users | Centralized user management content.

Basic user role for Compass

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Apps (Apps > Atlassian apps).

3. Search for Compass.

   • If there are no results for Compass instances in the organization, then no action is required. Skip to the next section.

4. For each Compass instance in the results:

   1. Select Manage app (••• > Manage app).

   2. For each group that is not marked as default group:

      1. Select the Roles drop-down and un-check Basic, if checked.

   3. For each group that is marked as a default group:

      1. Select the Roles drop-down and identify whether Basic is checked.

         • If not, no action is required. Move to the next group.

         • If so:

           1. Select the group name to view its details.

           2. For each member of the group:

              1. Select ••• > Remove member from group.

              2. Review the prompt and select Remove from group to confirm.

Stakeholder role for Jira Service Management

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Apps (Apps > Atlassian apps).

3. Search for Jira Service Management.

   • If there are no results for Jira Service Management instances in the organization, then no action is required. Skip to the next section.

4. For each Jira Service Management instance in the results:

   1. Select Manage app (••• > Manage app).

   2. For each group that is not marked as default group:

      1. Select the Roles drop-down and un-check Stakeholder, if checked.

   3. For each group that is marked as a default group:

      1. Select the Roles drop-down and identify whether Stakeholder is checked.

         • If not, no action is required. Move to the next group.

         • If so:

           1. Select the group name to view its details.

           2. For each member of the group:

              1. Select ••• > Remove member from group.

              2. Review the prompt and select Remove from group to confirm.

Contributor role for Jira Product Discovery

1. Log in to https://admin.atlassian.com and select the organization for which you’d like to disable the centralized user management experience.

2. Navigate to Apps (Apps > Atlassian apps).

3. Search for Jira Product Discovery.

   • If there are no results for Jira Product Discovery instances in the organization, then no action is required. Skip to the next section.

4. For each Jira Product Discovery instance in the results:

   1. Select Manage app (••• > Manage app).

   2. For each group that is not marked as default group:

      1. Select the Roles drop-down and un-check Contributor, if checked.

   3. For each group that is marked as a default group:

      1. Select the Roles drop-down and identify whether Contributor is checked.

         • If not, no action is required. Move to the next group.

         • If so:

           1. Select the group name to view its details.

           2. For each member of the group:

              1. Select ••• > Remove member from group.

              2. Review the prompt and select Remove from group to confirm.

Request the centralized user management experience be disabled

Once you have reviewed the organization ensure that all of the above requirements have been met, you can contact Atlassian Support to request the centralized user management experience be disabled for the organization. Be sure to include the following details in your request:

• The organization ID or the URL of a site that’s managed by the organization.

• Your acknowledgement of the following changes once the centralized user management experience has been disabled:

• Users and groups will be managed at the site level instead of the organization level. As such, the Users and Groups menus will no longer be available via the Directory tab in the Admin Hub—you'll need to use the Users and Groups menus for the site instead.

• The Domains menu will move from the Settings section to the Directory section of the Admin Hub.

• A new Administrators menu will be available under the Settings tab of the Admin Hub. Instead of managing users' organization admin permissions via the Users page under the Directory tab, you will need to use the Administrators page under the Settings tab.

• The User access admin role will no longer be available.

• The Basic user role for Compass, the Stakeholder role for Jira Service Management, and the Contributor role for Jira Product Discovery will no longer be available.

• All Organizations REST API endpoints that specify "The API is available for customers using the new user management experience only" will no longer be available to your team.