When multiple users in your Atlassian Cloud site need the same permissions or restrictions, you can add the users to a group and then set permissions on the group.
To create, delete, and edit groups:
- Go to > Site administration.
- Select Groups from the left side of the page.
- Do either of the following:
- Choose in the sidebar to create a new group. > Create a group
- Select a group to add or remove users, edit it, or delete it.
Keep in mind the following when working with groups:
- When users are created, they're automatically added to a default group, depending on which products you use in your Atlassian Cloud service.
- You can't add Jira Service Desk end users (i.e. those submitting service desk requests) to any groups.
Default groups and permissions in Atlassian Cloud
Products in Atlassian Cloud are set up with some default groups (and permissions assigned to those groups). Users are automatically placed in the '[product]-users' group when you give them application access to the corresponding product. The '[product]-users' group allows users to access the product with basic permissions. You can further restrict the users' access within a product by using the product's permissions.
Depending on when you created your site, there might be slight differences in the default groups that exist in your instance.
|In this product||Default groups||Default permissions|
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 Jira products:
Typically, you add users who work on issues 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.
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:
Users with this permission are considered site administrators for documentation and Support purposes, and they have access to all the products in the site.
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.
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
The 'Jira Users' and 'Bulk Change' global permissions.
A member of the 'Users' project role, which allows members to see all project issues (unless protected by a security level) and create new issues.
the permission to create and view Confluence content for the project, create personal and global spaces
Jira Service Desk
Jira Service Desk uses this group to manage license allocation. Users in this group count towards the Jira Service Desk license.
In addition to these groups, there are two default groups that are used by Atlassian support staff. You can't edit these groups or add users to them:
The 'sysadmin' user from these groups can log into 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 placed in.
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.