One permission set for one project?

[James Childs]

Is it standard to assign a one permission set to one project?  I have scenarios where the group of users is unique for each project and I need to give access only to their project whilst hiding the others.

It would appear that in order to achieve this, I need a unique user group and unique permission set for each project - is this correct?

[Steve Thornhill · Accepted solution]

Permission schemes can use Users/Groups/Roles to define the areas of access you require.

If you setup the permission scheme using a Role based method then that scheme can be used across multiple projects.

For each project with that scheme, you can then add the users or groups to the project roles to allow for access.

Further information on the Roles - https://support.atlassian.com/jira-cloud-administration/docs/manage-project-roles/

[Mark Segall]

Hi @James Childs - If you use project roles you can often share permission sets and then just assign individual users to the project roles.  For example, Developers may be different from project to project, but if each project has a permission set where a developer role is assigned appropriate permissions, you just need to add the individuals to those roles. 

Roles also enable you to empower project admins to manage their own projects rather than having to engage a Jira Admin every time they need to add someone new to their project.

Groups make sense when you have strict security policies where you want permissions to be managed centrally by a Jira Admin. 

[James Childs]

Thanks for reply.  So, use of Roles is not essential but a useful option to help with access control and permissions?

I am experimenting at the moment with a view to moving to company managed projects and keen to understand the easiest way to restrict project access but also ensure users have appropriate functional access within that project.

My current setup makes use of Groups and Permission Sets - it would appear I do need to introduce Roles too.