Jira Premium. Limit a role viewing and editing other projects

[BenWade]

Hi, guys,

Please guide me step by step.

I created a new project called 'DataQuality' and a new role: 'External.'

In total, I have 7 projects in Jira. I will add 10 more users to my Jira instance and assign them to the 'External' role in Project Settings -> People. These users should only see the 'DataQuality' project.

Somewhere in the forum, someone mentioned that the 'Browse Projects' permission is actually singular, meaning if you grant 'Browse Projects' to a certain role, then they won't be able to see other projects. But, as I found out lately, they actually can browse other projects as well if they go to -> Projects -> view all projects.

So how to assign permisisons properly? What should I do so this group can only see and manage 'DataQuality' project? Which permissions should I grant to this role- or I should use another menu?



Please, guide me step by step

[Trudy Claspill · Accepted solution]

Hello @BenWade 

Do you have only Company Managed projects, only Team Managed projects, or both types of projects in your Jira environment?

When you say that the users can "browse" other projects by going to the "View All Projects" page, do you mean simply that they see other projects on the list, or can they also select those projects and see the issues in the projects?

The Browse Projects permission within a Permission Scheme for Company Managed projects grants the user the ability to see the project for any project that uses that Permission Scheme. If that Permission Scheme is used by multiple projects, then the users can see all of those projects.

In addition, permissions to see Team Managed projects are handled separately, within each individual Team Managed project. A user may have the Browse Projects permission in a Permission Scheme assigned to only one Company Managed project, but that doesn't affect their ability to see Team Managed projects.

To limit a user to seeing one and only one project you have to grant them permission to that one project and then also ensure that the permissions on all other projects are configured in a way so that the user doesn't have permission to see those other projects.