Markin Jira project as ‘browsable’ or ‘not browsable’ by other projects’ team

[Kiran Somarajan]

how we can mark Jira project as ‘browsable’ or ‘not browsable’ by other projects’ team members.

[Airbus Driver · Accepted solution]

If I understood this correctly, you want to configure the permissions for projects such that members belonging to specific projects can/cannot browse them.

This is a good case for Project Roles.

Once you have configured the relevant project roles and added team members into the relevant roles, you can add them to the 'Browse Projects' permission.

[Kiran Somarajan]

if we have multiple projects in a Jira instance we dont want all members to have browse capability to all projects.

For example. 

Team member 1 has access to project A and he should not be able to browse project B

How can we configure this capability 

[Airbus Driver]

This is exactly what a Project Role is used for. Check out this video on how to configure Project Roles.

[Nic Brough -Adaptavist-]

>Team member 1 has access to project A and he should not be able to browse project B

Check the permissions scheme.  The rules in there determine who can see a project.  For Team Member 1, give them "browse project" in project A, and do not give them that in project B.

[Nic Brough -Adaptavist-]

Jira permissions are permissive, not restrictive.  If you want to stop someone doing something, you do not restrict them, you remove their permission to do it.

So, to stop team member 1 browsing project B, you need to look at what permission is letting them into project B and remove it.  It will probably be a role or group that 1 is a member of, granting the permission to browse the project (look at the permission scheme for project B)