Create and update groups
When multiple users in your organization need the same permissions or restrictions, you can add the users to a group and then give the groups product access. Learn how to manage product access
You can't add Jira Service Management portal-only customers (i.e. those submitting service project requests) to any groups. Learn more about managing portal-only customers
Create a group
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select Create group.
Enter the group’s details, including its name and members.
Select Create.
You’ll be redirected to the group detail screen. To give the group product access:
Select Add products.
Select a product role from the Product roles dropdown.
Select Add.
Edit a group
Edit name and description
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select the group whose details you want to edit.
Select the More actions icon (•••) next to Add group members.
Select Edit group name to rename the group.
Select Edit description to change the description.
Select Save changes.
You can’t edit the name of a group if it's used within some Jira administration settings or if it has a restricted or protected name. Some group name changes could have an impact on your apps. Learn about the details in our Community announcement
Edit or remove product access
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select the group whose details you want to edit.
To edit product access: In the Group product access table, select another role in the Product roles dropdown for the relevant product.
To remove product access: In the Group product access table, select the More actions icon (•••) next to the relevant product and select Remove product from group.
Delete a group
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select the group you want to delete.
Select the More actions icon (•••) next to Add group members.
Select Delete group.
Confirm that you want to delete this group, then select Delete group.
You can’t delete a group if it’s marked as a Default access group.
Update group membership
Add users
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select the group that you want to add users to.
Select Add group members and search for the users you want to add.
Select Add users.
Remove users
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Directory > Groups.
Select the group that you want to remove users from.
In the user table, select the More actions icon (•••) for the user you want to remove.
Select Remove member from group.
Confirm that you want to remove this user, then select Remove from group.
Default groups and permissions
Users are automatically placed in default groups (<product>-users-<sitename> e.g., jira-software-users-atlassian.com) when you invite users to a cloud product. The <product>-users-<sitename> group allows users to access the product with basic permissions. You can further restrict users' access within a product with the product's permissions.
Depending on when your site was created, there may be some differences to your site’s default groups.
For instances created after August 2021
In this product | Default groups | Default permissions |
|---|---|---|
Org-wide groups | site-admins | Contains users who manage all your sites and the organization. The following default permissions are available for site-admins:
Users with these permissions are considered organization administrators for documentation and support purposes. |
Jira Software | jira-software-users-<site-name> | Grants access to the Jira Software product under <site-name>. Assigns all members the 'Users' project role, which allows members to see all project work items (unless protected by a security level) and create new work items. |
Jira Service Management | jira-servicemanagement-users-<sitename> | Manages license allocation for Jira Service Management. Members of this group count towards the Jira Service Management license. This group has the ‘Jira Service Desk agent access’ global permission. |
Jira Work Management | jira-workmgmt-users-<sitename> | Grants access to the Jira Work Management product under <site-name>. Assigns all members the ‘Users’ project role, which allows members to see all project work items (unless protected by a security level) and create new work items. |
Jira Administration | jira-admins-<sitename> | The default permissions granted to this group depend on the products you have. For example, if you have Jira products only, the group permissions will include only the Jira product permissions. In Jira products:
|
Confluence | confluence-users-<sitename> | Assigns the global permission to create and view Confluence content for the project, and create personal and global spaces. |
confluence-admins-<sitename> | This group has the 'Confluence Administrator' global permission. Confluence admins are granted the ‘confluence-users’ default permissions. Users in the 'administrators' group have product access to Jira products, and therefore, require a Jira license. If you have users in the 'administrators' group that you don't need/want to take up a Jira license, you can create a new group, such as 'confluence-admins,' that you can use for admins that don't require a Jira license. | |
Opsgenie | opsgenie-users-<sitename> | The permission to access the Opsgenie product, which may include creating and editing Opsgenie alerts and schedules. |
Statuspage | statuspage-users-<sitename> | The permission to access the Statuspage product and view any pages. |
statuspage-admins-<sitename> | The permission to access the Statuspage product and manage user access to pages. |
For instances created before August 2021
In this product | Default groups | Default permissions |
|---|---|---|
Site-wide groups | users | For instances created before February 2014, this was the default group that new users were added to. In instances created after that date, all new users will be added to the '[product]-users' group for the product(s) they have access to instead of the 'users' group. The default permissions granted to this group depend on the products you have in your service (for example, if you have Jira products only, the group permissions will include only the Jira product permissions). In Jira products:
In Confluence:
|
jira-developers | In Jira products:
Typically, you add users who work on work items to this group. You can add users to this group from the Users page. This group is named 'developers' in Jira instances created earlier than February 2014. | |
administrators | The default permissions granted to this group depend on the products you have (for example, if you have Jira products only, the group permissions will include only the Jira product permissions). In Jira products:
In Confluence:
Users in the 'administrators' group have product access to Jira products, and therefore, require a Jira license. If you have users in the 'administrators' group that you don't need/want to take up a Jira license, you can create a new group, such as 'confluence-admins,' that you can use for admins that don't require a Jira license. | |
trusted-users-<id> | The users in this group have the Trusted role.
This group is not visible on the Groups page of your site. Users get added to this group when you set their role via the Role selector on the Invite users page or the user details page. This group is visible from the Jira and Confluence global permissions. | |
site-admins | Site-admins are the users who manage a site. The following permissions are currently available to site-admins:
Users with this permission are considered site administrators for documentation and Support purposes, and they have access to all the products in the site | |
All Jira products | jira-users | The 'Jira Users' and 'Bulk Change' global permissions.
A member of the 'Users' project role, which allows members to see all project work items (unless protected by a security level) and create new work items. |
jira-administrators | The same default permissions assigned to the 'administrators' group, for only Jira products.
| |
Jira Software | jira-software-users | A member of the 'Users' project role, which allows members to see all project work items (unless protected by a security level) and create new work items. |
Jira Service Management | service-desk-agents | Jira Service Management uses this group to manage license allocation. Users in this group count towards the Jira Service Management license.
|
Confluence | confluence-users | the permission to create and view Confluence content for the project, create personal and global spaces |
Opsgenie | opsgenie-users | the permission to access the Opsgenie product, which may include creating and editing Opsgenie alerts and schedules. |
In addition, there's a default group system-administrators used by Atlassian Support staff. You can't edit this group or add users to this group.
The 'sysadmin' user from this group can log in to your site to provide support to you and to perform certain system maintenance tasks. This user automatically has full product access but does not count towards your license limit, no matter which groups it is added to.
The account is only used by Atlassian. You may notice logins by this user even without having raised a support request. This is because certain types of system maintenance involve our automated systems performing tasks using this account.
Was this helpful?