You can't add Jira Service Management portal only customers (i.e. those submitting service project requests) to any groups.
Create groups
- Go to your site's Admin at admin.atlassian.com. If you're an admin for multiple sites or an organization admin, click the site's name and URL to open the Admin for that site.
Select Groups from the navigation menu.
Select the Create group button to create a new group.
Enter the Group’s name, the group description, and select wether you’d like to add users to the group right away.
Save the group by selecting the Create group button.
If you selected the Add members in the next step checkbox, select users to add to the group.
Edit and delete groups
- Go to your site's Admin at admin.atlassian.com. If you're an admin for multiple sites or an organization admin, click the site's name and URL to open the Admin for that site.
Select Groups from the navigation menu.
Select a group from the list to edit or delete.
Edit the group description by clicking the Edit description button.
- Edit the group's product access by clicking Edit group's access under Group access. See Update product access settings for more details.
Delete the group by clicking the Delete group button.
You can’t delete groups marked as Default access group.
Update group membership
- Go to your site's Admin at admin.atlassian.com. If you're an admin for multiple sites or an organization admin, click the site's name and URL to open the Admin for that site.
Select Groups from the navigation menu.
Select a group from the list where you want to add or remove users.
To add users to the group, click Add members, select the users you’d like to add, and press the Add button.
To remove users from the group, press the Remove button next to each user’s name.
Default groups and permissions
Users are automatically placed in default groups ([product]-users) when you invite users to your site and choose a product for them to access. The [product]-users 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 you created your site, there might be slight differences in your site’s default groups.
| 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 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. | |
| 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 issues (unless protected by a security level) and create new issues. |
| 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 issues (unless protected by a security level) and create new issues. |
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 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:
- confluence-administrators
- system-administrators
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.