How to restrict access to "Browse project" feature permission?

[Mohajit Acharya]

Requirement:

Users of Project A should not see or browse any other project except Project A

Solution tried: I have tried the solution mentioned by Maxime Boulat in his article:

https://projectbroadway.atlassian.net/wiki/spaces/MW/pages/1854308485/Discovering+Jira+user+management 

Steps:

1. Created a dedicated User Group ("User Group A") and added all the users to this group

2. Create a dedicated Project Role ("Role A") and have given all the users of "User Group A" access to this "Role A"

3. Created a Permission Scheme ("Scheme A") and have given "Browse Project" feature access based on the Project Role i.e. "Role A"

4. Have revoked the "Application Access" permission from "All logged-in users" of the "Browse Project" feature from the "Default software scheme" permission scheme

5. Have associated "Scheme A" to "Project A"

How to make this or any solution scalable?

With the above solution, I am finding it difficult to scale up as I have to replicate this for all the projects where I want to ensure that Users of Project A should not be able to browse Project B, C, D, etc., and vice versa. I have 25 such projects as of now. Is there a simpler approach to implement this requirement or am I missing something?

Thanks in advance!

Note: Looking for an OOTB solution, not through any plugins.

[Mohajit Acharya · Accepted solution]

Below KB article has helped me in cracking this requirement. Thank you.

https://confluence.atlassian.com/cloudkb/how-to-restrict-project-access-for-teams-in-jira-cloud-953142266.html 

[Arnav · Accepted solution]

Hi all,

I have 50 projects. for every project we are using the same permission scheme. with that the user who logged into jira they can able to view all projects.

 I have removed BROWSE PRMISSION- application access -'Any logged in users". 
But my query is ,although I have removed "any logged in users permission "they can view all the projects like before.
How to find out the user is working for respective project and he should have visibility for that project only. 
Is there any simple way to find out without doing it  manually?

[Jack Brickey]

Let me attempt to assist using an example:

users Fred & Wilma should have access to all projects

users Barney & Betty should only have access to project ABC

User Management - Barney & Betty belong only to "abc-only" group, Fred & Wilma belong to a generic default group like jira-software-users

Project ABC Permissions include but not limited to:

• Browse includes: jira-software-users, abc-only
• include the same groups for things like: Assignable users, Close issues, create issues, etc. to meet your needs

ALL other projects:

• ensure you do not use "Any logged in user" on any permission Fish
• ensure you do not use "abc-only" on any permission

Log in as Barney and verify that they cannot access any project other than ABC. Repeat for Betty.

I have intentionally not gone down the scheme path here as I simply wanted to illustrate the basic concept. Schemes will help you simplify the above for very large instances with many projects.

[Mohajit Acharya]

Thanks a lot, Jack