Restricting Access to the 'People' Section in Jira Project Settings

[Nachiket Bal]

In our organization, we manage user access centrally through a dedicated user management system. To ensure consistent and centralized control, we currently restrict our Jira Project Admins from accessing the Project Settings page. This restriction is in place because the "People" section within Project Settings allows Project Admins to manage users directly, bypassing our central management process.

Is there a way in Jira to specifically hide or restrict access to the "People" section within the Project Settings, allowing Project Admins to access other parts of the settings while ensuring only Site Admins have visibility and control over user management?

[Marc - Devoteam]

Hi @Nachiket Bal 

You can stop using roles in the permission schemes used on the project, base the permission schemes fully on groups and users.

Then when in the people section a users is added to a role, this will have no impact at all, as no roles are then specified in a permission scheme.

[Nachiket Bal]

@Marc - Devoteam  This solution probably lands us in the same situation since if we use groups and the groups are associated with the permission scheme, the users who are part of it that need access to the project settings page, they would still have access to the people section

[Florian Bonniec]

Hi @Nachiket Bal 

Because People section access is granted to project admin, there is no way to prevent user to access this section but allow them to manage other project admin feature.

Regards

[Nachiket Bal]

@Florian Bonniec  That's what I figured, but wanted to check within the community if folks have found any innovative way of doing it. Possibly for Atlassian to consider, now that they are rolling out granular permissions to control, workflows, screens and fix version.

[Florian Bonniec]

There is some request to like this one [JRACLOUD-34015] Separate Project permissions for Version Management - Create and track feature requests for Atlassian products. to have more granular permission.

I checked and did not find a way to catch Role membership change, so you could have been able to remove it if anyone updated the role membership.

[Nachiket Bal]

Thanks @Florian Bonniec  I did not see it either. Let me request a feature request on the Atlassian backlog similar to the version control via our Atlassian POC. Once I get a hold of ticket I will share it here for voting. In the mean time if you find any other solution please let me know.