Setting permissions for a Project Manager (Company Managed)

[John Bradley]

Hello, I've been given the task of setting up permissions for our project manager in Jira and could use a little help. I'm fairly new to being a Jira Admin.

We currently have nine projects that use one permission scheme. Up until now, Atlassian administrators have been Project administrators.  

The main concern is that we do not want the Project Manager to delete any projects or filters, but can create them.  

What would be the key permission differences between the Jira Admin and the Project Manager I should consider?

Thank you,

John

[Yousuf Raza]

As a Jira Admin, you have complete control over the Jira instance. You can manage global settings, system settings, users, and all projects. Project Managers do not have global admin rights and cannot delete projects.

You can set up permission schemes associated with your projects and assign project permissions to the Project Manager role, such as creating issues, editing issues, browsing projects, etc. Make sure to only assign the Project Manager role the permissions they need, and ensure that delete projects or filters and global admin permissions are not included.

You can learn more on how to manage and exclude specific permissions so the project manager role does not have the ability to delete projects or filters, please review this documentation on project permissions on Jira.

[Mikael Sandberg]

Jira project admins only get elevated permissions within the project, they will not be able to remove filters that they are not the owner of nor will they be able to delete projects. All they will be able to do is administrate some features within the project like changing the issue layout, adding/removing access for users to the project, adding /removing components etc. Outside of the project their permission is the same as any other user that are not Jira admins.