Dear Atlassian Support Team,
We would like to request clarification regarding the upcoming change to direct assignment of the Organization Admin role, as announced in the following article:
We are concerned about the potential impact on our existing Jira Service Management (JSM) permission configuration and our administrator management procedures.
We would appreciate your confirmation of the expected behavior both during the transition and after the rollout is fully completed.
1. Our current environment and permission configuration
Our Atlassian organization/site is dts-ops-service.
We currently manage administrator permissions using the following configuration.
1.1. Organization administrator group (org-admins)
The org-admins group currently has the following app roles assigned:
- Jira Administration — App admin
- Jira Service Management — User (agent)
- Confluence — App admin and User
- Assets — App admin and User
- Studio — App admin and User
- Other app roles configured in our organization.
In addition, we have added the org-admins group to the Administrators space role in our existing JSM spaces.
As a result, users belonging to this group currently receive Jira administration permissions and the relevant JSM space permissions through the existing group configuration.
1.2. Jira administrator group (jira-admins-dts-ops-service)
We also have a separate group for users who require Jira administration permissions without Organization Admin access.
The group currently has these app roles:
- Jira Administration — App admin (default)
- Assets — App admin
- Studio — App admin
These users are generally also members of the first-level or second-level maintenance groups for specific JSM spaces.
Those maintenance groups are assigned to the Service Desk Team space role in the corresponding JSM spaces.
Therefore, the Jira administrator group and the JSM maintenance groups serve different purposes in our permission model.
1.3. How we currently manage permissions
We manage administrator permissions manually through the Atlassian Administration UI. We do not use APIs, scripts, or automated provisioning to grant or revoke administrator roles.
Our existing operational procedures have used the org-admins group when granting Organization Admin and Jira Admin access.
However, following the announcement, we have been investigating the direct role assignment method available in the user profile.
We tested assigning and removing the Organization Admin role through the UI. During our tests, we observed that users were also automatically added to or removed from the org-admins group.
We would like to confirm whether this synchronization is part of the officially supported behavior or whether it may change after the rollout.
2. Questions regarding the new specification
A. Organization Admin assignment and removal through the UI
Q1. Official UI procedure
After the change, is the following the officially recommended procedure for granting the Organization Admin role?
Atlassian Administration → Directory → Users → Select user → More actions (•••) → Assign organization admin role
Similarly, should we remove the Organization Admin role through the corresponding role-removal action in the user profile?
We have attached a screenshot of the assignment option currently displayed in our environment.
Q2. Group-based role assignment
After the rollout, is it correct that manually adding or removing users from the org-admins group through the Atlassian Administration UI will no longer grant or revoke the Organization Admin role?
Does this behavior apply regardless of whether the group is managed through the UI or another mechanism?
B. Relationship between direct role assignment and org-admins membership
Q3. Automatic group membership when assigning Organization Admin
When we directly assign the Organization Admin role through the UI, will Atlassian continue to automatically add that user to the org-admins group?
We observed this behavior during our tests.
Is this behavior guaranteed after the migration is fully completed, or is it only temporary behavior during the transition?
Q4. Automatic group membership removal when revoking Organization Admin
When we directly remove the Organization Admin role through the UI, will Atlassian automatically remove the user from the org-admins group?
We also observed this behavior during our tests.
Will this synchronization continue after the rollout is completed?
Q5. Independent role and group membership states
After the change, will the following states be possible?
- A user has the Organization Admin role but is not a member of
org-admins. - A user belongs to
org-admins but does not have the Organization Admin role.
If either state is possible, how does Atlassian recommend managing the relationship between direct Organization Admin assignments and org-admins group membership?
C. Impact on Jira Administration and JSM space permissions
Q6. Jira App Admin permissions
When the Organization Admin role is directly assigned, is the Jira Administration — App admin role also granted automatically?
If so, is it granted through the org-admins group membership, or independently through the direct Organization Admin assignment?
We would also like to know what happens to this App Admin role when Organization Admin access is revoked.
Q7. Existing JSM Administrators space role
In our environment, the org-admins group is already assigned to the Administrators space role in our existing JSM spaces.
If a user receives the Organization Admin role through direct assignment but is not automatically added to org-admins, will that user still have the Administrators space role in those JSM spaces?
If not, would we need to assign the relevant JSM space permissions separately?
Q8. Remaining Jira/JSM permissions after Organization Admin removal
If a user's Organization Admin role is removed but their org-admins group membership remains, will they retain the permissions granted through that group, including:
- Jira Administration — App admin
- Jira Service Management — User (agent)
- Confluence — App admin and User
- Administrators space role in existing JSM spaces
We are particularly concerned about users retaining Jira/JSM administrative access after their Organization Admin role has been revoked.
Q9. Recommended group configuration for JSM space administration
Is it still supported and recommended to assign the org-admins group to the Administrators space role in JSM?
If direct Organization Admin assignments and group membership are no longer guaranteed to remain synchronized, would Atlassian recommend creating a separate group specifically for JSM space administration?
Would any changes to our existing space role configuration be necessary?
D. Migration impact, verification, and future operations
Q10. Impact on existing configuration
During the migration to direct Organization Admin role assignment, will Atlassian preserve the following existing settings?
- Current
org-admins group memberships - App roles assigned to
org-admins - Existing JSM space role assignments referencing
org-admins - Existing Jira administrator group configurations
Will Atlassian automatically modify any of these settings as part of the migration?
Q11. Rollout status for our organization
How can we determine whether the new role assignment model has already been fully enabled for our organization (dts-ops-service)?
Is there a way to verify the migration completion status or the expected rollout date through the Atlassian Administration UI?
Q12. Recommended post-change verification
After the rollout, what is the recommended way to verify the following information through the Atlassian Administration UI?
- Which users have been directly assigned the Organization Admin role
- Whether a user belongs to
org-admins - Whether a user effectively retains Jira Administration — App admin permissions
- Whether a user has the required Administrators space role in a particular JSM space
We would appreciate an officially supported verification procedure that we can incorporate into our operational documentation.
3. Purpose of this inquiry
Based on your answers, we would like to determine whether the new specification requires changes to:
- Our existing JSM space permission configuration.
- Our Organization Admin and Jira Admin assignment/removal procedures.
- Our procedures for setting up permissions in newly created JSM spaces.
- Our administrator permission verification procedures.
- Our user and administrator access inventory.
We would particularly appreciate clarification on whether the automatic synchronization between direct Organization Admin assignments and org-admins group membership, which we currently observe, will remain officially supported after the rollout is completed.
If possible, please provide references to official documentation describing the expected post-migration behavior.
Thank you for your assistance.
Best regards,
DTS Software Vietnam