How do I grant users limited read only access?

I need to grant access to a few people so that they may "observe" some of our projects and scrum boards.

I do not want them to be able to inadvertently change anything.  We have more than 20 projects, and I only want to allow them access to 4. 

How is this done in JIRA?

2 answers

1 accepted

Just give them the "Browse Project" permission. If I were to implement it, I will create a Role called "Viewers" and add the "Viewers" role in the "browse project" permission on whatever permission scheme that project is using.

Browse Projects

Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted viaIssue Security). Many other permissions are dependent on this permission, e.g. the 'Work On Issues' permission is only effective for users who also have the 'Browse Projects' permission.


@Gabrielle BautiIn our Project we have three boards, where the teams are sprinting, all of them are Scrum boards. Each board focus on a particular phase of the project. Then we will like to have a global board, for example a Kanban board. With the intention to visualize the entire project life-cycle. This board is going to be just a read-only. They have to go to specific Scrum board to move the issue from one column to another one. My question is: Under you approach would be possible that a project member could have full access to Scrum board, but just read-only access to the mentioned Kanban board within the same project? Thanks. 

@Gabrielle BautiIs it possible to implement this solution for a specific board of the project, i.e. give full permission to the user in one board and then just read-only access for a second board within the same project? thanks

Hi @Fred Anderson,

You could assign this group of people the browse permission only for those 4 projects.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

392 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you