How to ONLY give access to people in the company managed project?

[Max]

I am setting our environment up and am running into a some issues.

What I want is that only people in the project to see the projects when they browse trough the projects. This is for security reasons and for more focus. We don't want to bother with information people dont need.

We have multiple projects (all company managed) with multiple external partners.
We don't want the different external parties to look into each others projects.
In these project we have several internal team members.
Some need access to all project some to  just one specific.

I have read multiple threads on this now and there doesn't seem to be a simple solutions.
The way team managed project can be set to Private would be ideal but I can't find this option in the company managed projects.

[Sarp Egemen · Accepted solution]

Hi @Max ,

Company-managed projects are configured through schemes assigned to projects, one of which is the well-known "Permission Scheme." If you want certain people to see all projects and others to see just one or two, there are multiple approaches to achieve this.

Note: for a user to view a project, they need the "Browse Projects" permission.

1st Way (IMO better approach):

Use a single permission scheme and create a project role called "Viewer" or "Member" (or whatever name you prefer). Then, grant the "Browse Projects" permission to this role using the permission scheme.

With this setup, you can navigate to each project's Settings → People section and assign a group or user to the role, allowing them access to the project.

2nd Way:

Create different permission schemes for different projects. While this approach reduces standardization and increases administrative effort, it offers greater flexibility in configuration.

With this method, you can directly assign the "Browse Projects" permission to a group or user in the permission scheme itself. This eliminates the extra step of assigning roles within individual projects but requires you to manage multiple schemes.

[Max]

Hi Sarp,
Thanks for you answer.

This seems like a good option.
Just to be sure, would this work?

I create the role "project member".

Add person 1 to project 1 with role Project Member.
Add person 2 to project 2 with role Project Member.

Would they see each others project?

[Max]

Just to let everybody know it works with the project manager role.
We have one role and now everybody can only see the projects he is a part of.

[Sarp Egemen]

Hi @Max ,

I'm happy to hear that the solution worked!

Regarding your previous question, as you mentioned also, users don't see each other's projects and only have access to the projects they are assigned to.

This is because, in Jira, Project Roles are scoped to individual projects. This means that the role you assign to a user in a specific project is only valid within that project, even if the role exists in a permission scheme that is shared across multiple projects.

All the best,

[Trudy Claspill]

Hello @Max 

For Company Managed projects access to the projects is governed by the Browse Projects permission within the Permission Scheme associated to the project.

To limit project visibility to members of just that project, you will need to modify the Permission Scheme(s) associated to that project to grant the Browse Projects permission to only users in Project Roles in that project.

Make sure that you also leave that permission granted to the Project Role atlassian-addons-project-access to ensure automation and third party apps work correctly.

Refer to this documentation:

https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/

[Petru Simion _Simitech Ltd__]

@Max 

Each project allows, throught the permission scheme, setting who can do what in that project.

A permission scheme can either assign permissions to individual users, group of users or roles. 

Roles are defined within each project and each role can contain either individual users or groups.

While this configuration is already convoluted for a project, it becomes even harder to see the whole picture across an organisation.

If you are open to using apps, you can use Roles Dashboard for Jira, an app released by our company.

https://marketplace.atlassian.com/apps/1235459/roles-dashboard-for-jira?hosting=cloud&tab=overview

The Project - Role - User Relationship tab and the User-Role-Project relationship tab views are exposing the overall picture of how users, groups and roles are related in your enterprise.

You can either fetch the whole data, or filter by projects and/or roles, export your data to cvs for further analysis and storage.

Regards, 

Petru