Permission to browse projects

[BenWade]

Hi everyone,

I am configuring the permission scheme. I do not want to go over each project permission.

1) If I grant a 'Browse Projects' permission to a Developer role, do I need to go one by one and add Developer Role to Issue Permissions, Comments Permissions, Attachments Permission, etc?

2) If I remove 'Any Logged in user' from 'Browse Projects', will I need to remove 'Any logged in user' one by one from other permissions or not since 'Browse Projects' includes the ability to browse projects and the issues within them? So, by definition, if this role is removed, then users have to be restricted from the permissions below this level (Issue permissions, Comments Permissions, and so on).

One more question, 'Browse projects' refers to 'this' project(singular) and not all projects in JIra, right?

[C_ Derek Fields · Accepted solution]

Adding to what @Trudy Claspill responded, you can add a set of permissions at one time to a role or group or user. Instead of going one-by-one, you use the "Grant Permissions" button. This will ask you to select the type of user you are adding and then you can select all of the permissions that role should have. This is a time-saver over doing it permission-by-permission.

On the other hand, to remove a role from permissions, you still need to do it one-by-one. However, you generally don't have to remove all of the permissions. If you remove Browse Projects and Create Issue, there isn't anything that the user can do in the project.

[Trudy Claspill · Accepted solution]

Hello @BenWade 

1. If you grant a role the Browse Projects permission, that only gives the role members permission to see the issues. If you want them to be able to do anything else, then yes you have to grant the role additional permissions.

2. As per this document:

https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/

"When a user is granted the Create issues permission for a project, they’ll see the project on the Create issue screen, even if they don’t have the Browser Projects permission for the same project."

So, users that don't have Browse Projects but do have Create Issue could still create issues in the project. But they would not be able to see the project otherwise, nor view/search for the issues in it.

The referenced document provides more information about what other permissions are dependent on having the Browse Projects permission.

3. Browse Projects does refer only to the project that uses the permission scheme. Multiple projects can use the same Permission Scheme, and the permissions in that scheme apply to each project that uses the scheme.