Review Incorrect License Count for Jira Service Management Cloud Agents
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
The count of Jira Service Management licenses exceeds the number of users in the jira-servicedesk-users group.
Solution
Why is the count higher than expected?
License count reflects every group that grants JSM agent access — not just jira-servicedesk-users. A user in any agent-access group (often via IdP/SCIM mapping) consumes a license.
Checking the product access
Please note that you must be logged in as a user with site-admin access to perform the following steps.
As a site-admin, list every group that has the Jira Service Management product/agent access.
If using SCIM, review your IdP mappings to ensure only intended agents are assigned to agent-access groups.
Remove non-agents from those groups to release licenses.
User Management Experience
In Jira's left panel, click on Jira settings > User management.
On the Admin panel, click on Product access.
The groups with agent access are listed below Jira Service Management.
Any user granted access to the Service Management application will be added to the default access group.
Another configuration to keep an eye on is users added to the Trusted Role.
This role will automatically grant all application access to the user.
Improved User Management Experience
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products from the header.
You will see the user count listed beside the product.
Clicking Manage Users takes you to the licensed users list.
Clicking Manage Product Access takes you to the groups with product access.
In the Improved Experience, the Trusted role no longer exists.
Remove groups from product access
Now that you have identified which groups grant users Jira Service Management agent access and which users are in the Trusted Role, you can go ahead and remove those that should not be granted licenses.
For SCIM-enabled IdPs:
Access your IdP settings and review SCIM group mappings. Ensure that only agent-designated groups are mapped to jira-servicemanagement-users or to any group that grants agent permissions.
Update SCIM assignments so that non-agents are mapped to customer or other appropriate user groups, not to groups that grant agent roles.
Save the settings and verify the accuracy of group membership in Jira administration.
For Users in the groups:
Select the group that you want to remove and click on ••• > Remove group.
Check if the license count matches the number of users on jira-servicedesk-users group and other default or custom groups granting Jira Service Management access. Be aware that changes to roles or group permissions will immediately affect billing and license counts.
For users in the Trusted Role:
Access the user's profile and change their Role to Basic.
Now toggle off the application access of Jira Service Management.
The invoice will depend on how many agents you have on your instance, it means people with the product enabled on their profile and not the Service Management agent permission in the project.
After removing non-agents, the JSM agent count in admin.atlassian.com > Billing drops to match your intended agent list.
Was this helpful?