You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Many customers have asked for a new role to allow them more flexibility when delegating administrative permissions to manage users. To address this, we're excited to introduce the user admin role to admin.atlassian.com. It will replace two of our current roles – trusted user and site admin.
The following example shows an organization (Acme), with one site (acme.atlassian.net) and two products: Confluence and Jira Software. The User admin role has been applied to a user for Confluence only (but it can be applied to any product if you like). A deeper explanation of the user admin role is below, read on!
This example illustrates the existing and new admin roles for an organization with one site and two products. You can set the user admin role for all products if you like.
All customers across all plans – Free, Standard, Premium, and Enterprise – will be able to use this new role to delegate user management for admins to specific products.
Existing organization admins (org admins) will have the choice to set their current trusted users and site admins to:
the current org admin role
the new user admin role for their existing products
additionally, their product access can be chosen for existing products
no admin role
When we migrate an organization to the new admin experience, we’ll provide a workflow for org admins to grant or deny the new user admin role to their current trusted users and site admins.
Before migration, org admins can minimise any impact to their trusted user and site admin users by changing them to org admin or basic user roles earlier. This isn’t necessary to do upfront, but it can help to make your migration more seamless for these users.
This is a high level example of the workflow to migrate site admins and trusted users.
With the latest changes to admin.atlassian.com, we’re in a better position to build more delegated admin roles, address a lot of our customer feedback, as well as help scale administration for our larger customers.
The biggest piece of customer feedback we get around our admin roles, is how trusted user and site admin roles force users to be granted access to product content – and are therefore paid for/billable – even if they may not use those products. With the new user admin role, these users don’t need to be granted access to the product content – and won’t be counted as a billable user.
There are three ways to add a user admin.
You can add the user admin role to a group for one or multiple products, then add users into that group. This will also work for groups synced via SCIM.
Coming late 2022
You can add a user admin role to an existing user, in the same way you would add any product access to them via the user details screen.
Coming late 2022
You can invite a user admin in the same way as inviting any other user.
Note: For those with keen eyes... Bitbucket will not be available as part of this update, we’re working on this as a future release.
We’re aiming to start rolling out the user admin role around mid-late 2022 and this will continue through to the start of 2023. About a month before we start to migrate an organization, we’ll send an email to the org admins outlining the migration plan.
The name User Admin could change before launch, but we wanted you to know all this as soon as possible! 😀