Are Project roles in the Permission scheme Project specific?

Question

Steps:

* In my Permission Scheme, I have assigned Browse Permissions to Project Role - Client.
* This permission scheme is used for 2 projects.
* Each project has separate users.
* Users are assigned with Project Role - Client.

Since both the projects are set to a scheme where users with the Clients roles can browse, can Client users browse both projects?

Or the 'People' page in the Project settings where we add the users to the roles which are project-specific, control the user permissions?

And when the permission says Browse Projects - does it mean browse only 1 project or all projects?

And lastly, which permission can provide the user to browse both projects other than setting Browse projects permission with 'Any logged in User'

Thank you in advance for taking the time to clarify the above.

Kapil Podduturi_8qvbeo · Answer

hi @Dave Bosman _Inetum_ ,

Thanks for your reply.

From your comment - 'Unless you also add him/her in the project role in that project.' - it means for the Project roles to work - Both adding the user into the project and in the correct role is compulsory. If one of them is not correct then the user will not have access to the project?

And for Team managed projects, how to restrict new client users to only have access to a Private team-managed project.

(should they be part of the default jira_software users group or should I create a new group or how to use project roles here)

Appreciate your time clarifying the above.

Thank you.

Kapil Podduturi_8qvbeo · Answer

.

Dave Bosman _Inetum_ · Answer

Hi @Kapil Podduturi

If you add project roles in your permission scheme, and you add a user in project A in that role, the user will not be able to see anything in project B unless you also add him/her in the project role in that project.

So it is really project specific.

If you want specific users to see all projects linked to the permission scheme, you have 2 options.

Option 1: Add the users to all the projects in the correct role.

Option 2: Create a group and add the users into that group. Then add the group to the permission scheme. This could be less safe: if you create a new project and use the same permission scheme the users from that group would also be able to see the new project and issues.

Regards

Dave