nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to restrict the project admin access for 'users& roles' section

Anu_xux0cy

I want to restrict the project admin access in particularly editing of the project role section . if the user is associated with admin access for the particular project,user should not able to add/edit or delete the users in project roles section.

is there any way to achieve this?

Accepted answers

All comments

Ollie Guan

Hi @Anu,

As far as I know, the current permission scheme cannot carry out such fine-grained management. You can refer to the following:

https://confluence.atlassian.com/adminjiraserver074/managing-project-permissions-881683464.html#Managingprojectpermissions-Extendedprojectpermissions

Grigory Salnikov_0hffsd

Hi!

To manage roles is one of the key project admin rights. In your case I would create a new "project admin" role and grant it all the needed permissions.

Anu_xux0cy

Thanks Ollie for the link. However 'Administer projects' roles comes with below package of permissions. .

"Administer projects

Permission to administer a project in JIRA. This includes the ability to edit project role membership, project components, project versions, and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description')."

If I remove the administer projects role in the permission scheme , admins won't be able to modify the components/versions .

We have around 6000+ users in the environment. I want to revoke the admin access only to 'user & roles' section.

Do you know any other way?

Anu_xux0cy

Hi Greg-this is not the case. As the system admin,I will taking care of the user access.

I want to restrict the access to "project admins"

Nic Brough -Adaptavist-

Ollie's description is correct, you cannot have partial admins.

You could do it by removing all roles from permissions, notifications and so-on, using only groups to grant access. This will, of course, leave your administrators in group-maintenance hell, but that is effectively your goal.

Anu_xux0cy

Thanks,but still this is not solve my query.

If the user/particular group is not part of the administer role users won't be able to work on the versions and components also. There is no way I guess to choose the particular actions as part of the administer functionality.

There should have been proper management options for the administer roles actions.When we have 5K +active users in the organisation, some functionality matters.