A focused admin role for JSM
For JSM owners managing multiple service spaces, portals and integrations, the new JSM App Admin role provides app-wide configuration access without granting access to unrelated Jira product settings. It supports least-privilege delegation while existing Jira Administrator permissions remain unchanged.
What it covers
JSM App Admins can manage service spaces from a consolidated app-wide experience; configure shared JSM settings, integrations, authentication, notifications and access; view audit and usage information where available; and manage space settings or archive spaces.
Scope matters: This role does not automatically grant Jira Software, Jira Work Management, Confluence or organization-wide user administration. It also does not include agent access on Jira Service Management
Where it fits
- Site Admin: Broad site-level administration across Jira apps, including JSM.
- JSM App Admin: App-wide JSM configuration and governance, without agent access or broad Jira Administrator access.
- Space Admin: Configuration of individual service spaces, including queues, SLAs, incidents and portals; a person can administer multiple spaces.
This additional layer gives JSM owners, service delivery managers, ITSM administrators and enterprise service management teams clearer ownership, less reliance on central Jira Administrators and a more clearly defined scope.
Getting started
- Organization administrators review which groups and individuals should keep the Jira Administrators App Admin role and which can transition to the new JSM App Admin role.
- Organization administrators assign the JSM App Admin role to selected individuals and groups for each JSM App.
- Organization administrators remove the Jira Administrators App Admin role from groups and individuals as required.
Community question:
As the role’s coverage expands, it will support a more consolidated JSM administration experience.
Which JSM tasks still require Jira Administrator access in your organization, and which app-wide settings and experiences should be prioritised next?
FAQ
Do I need to do anything for my existing JSM site?
No immediate action is required. Your existing JSM site and Jira Administrator permissions remain unchanged. When the role becomes available on your site, you can choose to assign JSM App Admin to people who need app-wide JSM administration without broader Jira Administrator access.
When can I expect this new role to roll out?
The role will begin rolling out this quarter, with rollout completion planned for December 2026. Check Atlassian Administration and official rollout communications for availability on your site.
Is the JSM App Admin role billable?
No. The JSM App Admin role itself is non-billable. If someone also needs to work on requests or queues, they need a separate billable role called User (agent). Individuals can hold multiple roles.
Why should I use JSM App Admin instead of Jira Administrators App Admin?
You can continue using your existing Jira Administrators App Admin permissions; this role does not remove them. For people whose responsibilities are limited to JSM, JSM App Admin offers a more focused, least-privilege way to delegate app-wide administration without granting access to unrelated Jira product settings.
What are App roles and how are they different from Space roles?
You can read more about App and Space roles and their capabilities here:
