Restrict access to Jira projects

[Brian Hoffman]

We set up a new project, added new Jira users, and added users to the new project. It appears that the new users can see all projects, not just the project they were added to. How can we restrict access to projects that users are assigned to?

[Trudy Claspill · Accepted solution]

Hello @Brian Hoffman 

Welcome to the community.

Are you working with Classic projects or Next Gen projects

As John said the Permission Scheme assigned to a project and the Browse Projects permission in what determines who can view the project.

The Permissions Schemes are about affirming access. You don't explicitly state in them "deny this permission to these groups/users".

What has likely happened is that the Permission Scheme assigned to your projects has granted the Browse Projects permission to a default user group, like jira-software-users, to which all licensed users get added. So when these new users became licensed and added to the default group, they became able to see all the projects accessible to that group.

To prevent them from seeing all projects, if they are Classic projects, you will have to modify the Permission Scheme(s) assigned to the project(s) to change which group(s) have the Browse Projects permission.

I don't work a lot with Next Gen project, so I can't speak knowledgeably about how permissions are managed for those.

[Brian Hoffman]

Hello @Trufy Claspill,

We are working with Next Gen projects. Your explanation makes perfect sense - thanks for taking the time to respond.

Brian.

[John Funk]

Hi Brian - Welcome to the Atlassian Community!

You can restrict access to a project by changing the Permission Scheme for the project. Update the scheme to change who has access to the Browse Project permission. 

[Brian Hoffman]

Thank you John. I will take a look at the Permission Scheme configuration.

[Mariano Lancellotti]

Hi John, what about Next Gen projects? I don't know how I can remove this permission. I don't want everyone to see other projects.

[Trudy Claspill]

@Mariano Lancellotti 

Welcome to the community.

Access to Next Gen projects is totally different. Refer to

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/

You will have to set the Access level on Next Gen projects to Private, and explicitly grant access on each project to the people who need access. The other Access options will enable all licensed user to see the projects.

[Mariano Lancellotti]

Thank you @Trudy Claspill for your help! I have set the project to private but the users still see the list of the projects. Maybe they can not access, but they can see the project names. I need to give access to 3rd party team.

[Sirvan Jackson]

@Trudy Claspill @John Funk 

I'm facing the same issue. I have 2 3rd party teams and I need to bifurcate the access. When I remove browse project option and sign in as them they have no active projects not even the ones they are assigned to, when I add browse project they see everything.

We use a handful of permission schemes so it doesn't make sense to create a scheme per project to have this specific control. 

I'm sure there is a work around. However, I can't seem to think of it.

Any ideas?

[Trudy Claspill]

@Sirvan Jackson 

Welcome to the community.

Please provide more information.

Please confirm - are you working with Jira Cloud?

Are you using only Company Managed projects, only Team Managed projects, or both in you instance?

What type of projects (Company or Team) do you need to grant access to for these teams?

What type of projects (Company or Team) are you trying to prevent them from accessing?

Why type of access do the 3rd party teams need - read only, edit, create, ...?

If you are trying to grant the 3rd party teams access to Company Managed projects, the individuals in those teams will need to be added to a User Group that has been

- granted Jira Software application access

- given the Browse Projects permission in the Permission Scheme(s) assigned to the projects you want them to access.

If you want to block them from browsing the contents of other projects while keeping those other projects accessible to you internal users, then you need segregate your 3rd party team members and your internal users into different User Groups, and assign the Browse Projects permission to the internal user group in the Permission Schemes assigned to those other projects

Permission Schemes don't affect the access to Team Managed projects. If you also have Team Managed projects where you need to grant access to internal users and block access for the 3rd party teams then you have to update each Team Managed project to use the Limited Access model, and then explicitly add the users/groups to each of those projects to grant them access.

[Sirvan Jackson]

Hi Trudy, 

Thanks for your response. Yes I'm using Jira Cloud and company managed projects.

The intent is to restrict access to company managed projects while preserving the access to projects I need the external team to work on. 

 "- given the Browse Projects permission in the Permission Scheme(s) assigned to the projects you want them to access."

The above is where I have an issue all the projects in question are using 1 permission scheme. I have already segregated the internal vs external into different groups. Then when I removed the external team from Browse Projects and they lose the ability to see projects.

Is the only way to do this effectively to have a separate permission schemes for each project?

[Trudy Claspill]

If all the projects currently share 1 permission scheme, then yes, you will have to create additional permission schemes. You will need one Permission scheme for each combination of User Groups that need Browse Projects permissions for the different projects.

I can't say if you need a separate scheme for each project. That depends on whether or not each project would need access granted to a different combination of User Groups.