Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,134
Community Members
 
Community Events
176
Community Groups

How can I properly edit/remove org-admins in the Old and New user management experience?

Hello, Everyone!

As you may know, Atlassian is deploying a new improved user management experience for products, which moves the user management of several applications (Jira Software, JSM, Confluence) to the organization-level, instead of site-level as it was done before. All new Atlassian organizations created are using this new experience by default, and we’re gradually migrating all the existing Atlassian products/organizations to this new model.

If you are an Org-admin, you can confirm your organization is already using this new experience by navigating to your organization at admin.atlassian.com and checking if the Users list and Groups list are under the Directory tab:

ede5324f-4cf1-480f-ade7-c6273a9458ed.png

This improvement has also changed the administration roles across Atlassian sites and organizations, as you can check below:

In the Old User management way, we had three levels of Administration:

  • Product admins – There are two types of product admins that have access to the Jira or Confluence settings:

    • Admins that belong to the administrator's group – administer product settings, but they also have access to the product themselves through this group.

    • Admins that belong to the <product-name>-admins groups – administer product settings, but they don’t have access to the product through this group.

  • Site admins – They administer the users and groups for the site’s products. They have access to the site's Admin and access to the products through this group.

  • Organization admins – They administer the organization and have access to the organization settings, which can be found at admin.atlassian.com.

In the new User management experience, we have only two levels of administration:

  • Product admins – They administer product settings depending on group memberships (e.g. Jira and Confluence settings). Not all product admins need product access (e.g. Jira Admins do not need product access to Jira Software or Jira Service Desk).

  • Organization admins – They administer the users and groups for the organization’s products, and have access to the organization settings which can be found at admin.atlassian.com.

Basically, the new UM experience has included the site-administrator role inside the Org-administrator role. That being said, we will provide in this article how you can properly change your organization admins considering all the current scenarios you might face in the new and old experience:

Scenario 1 - You are an organization admin, and you need to grant/remove another user with Organization admin rights:

  1. If you are using the new user management experience, you can follow the steps below:

    1. Log in to admin.atlassian.com

    2. From your organization, select Directory > Users from the left side of the page.

    3. Find the org-admin, then select their avatar or Show details.

    4. From the 3 dot icon at the top of the page, select Grant/Update organization role:
      fb4c5d43-92c4-4d31-823a-4dfa499296ef.png

    5. In the pop-up, click on  Remove Organization role or Add Organization role

  2. If you are using the old user management way, you can follow the steps below:

    1. Log in to your organization at admin.atlassian.com. If you have multiple organizations, click on the one you want to edit

    2. Choose Settings > Administrators:
      d8f09a4c-27cd-4a92-9f98-b44a8b4ab644.png

    3. If you want to grant Org-admin permissions, click Add administrators.

    4. If you want to remove Org-admin permissions, click on "Remove" under the actions column of the related user

Scenario 2 - You are not an organization admin and need to update yourself or another user with Organization admin rights:

In this case, you can follow one of the approaches below:

  1. Contact one of your Org-admins to perform the steps of scenario 1 and grant/remove the user with Org-administration rights.

  2. If you don’t know who might be the Org-admin(s) of your organization, contact Atlassian support and we will properly validate your request.

Scenario 3 - You are not an organization admin, and need to update yourself or another user with Organization admin rights, however, your current Org-admin(s) have left the company and their email account is not active anymore:

For the scenario above, you will need to contact your IT department to temporarily re-activate the email account of, at least, one of the Org admins. Once the Org-admin account is reactivated, you can log in with the reactivated account and follow the steps provided in scenario 1 to update a new user with Org-administration rights.

Important notice:

In this scenario, you may not be able to accomplish the reactivation of your account if you have 2FA enabled. If you step into this blocker, please contact Atlassian support describing your issue so we can properly help you reactivate the Org-admin account. We strongly recommend adding someone from your IT department as a request participant in the ticket if you contact Atlassian Support to deactivate 2FA, as this action will facilitate communication and speed up the resolution of the problem.

For scenarios 2 and 3:

If you are not a site-admin or billing/technical contact and require to contact Atlassian support, we suggest adding your site-admin as a request participant in the ticket in order to reduce the time taken to properly validate your request.

Thanks!

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events