nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

View only permission for project AND sprint/board

quinn_woodridge

I have scoured docs and the community to try to figure this out but I can't get Jira to function how I want it to. The bottom line is that I am trying to add an external client to a project so they may only see their project and everything inside of it, including active sprints, boards, the whole shebang.

I was able to get partially there with this post however, when doing it this way, the client can only see issues and cannot access anything else.

I have also tried to add the client to a group with site access and have the board Filter Shares (under general board settings) share with this group but this also has the unintended consequence of the client being able to see all projects because the whole group has site access.

The core requirement that I can't seem to get is the client access to active sprints and the boards within a project. I already have the issues working as mentioned above. Can this even be done with Jira or has someone found out and I haven't done enough research?

Thanks!

Accepted answers

Earl McCutcheon

Hi Quinn,

The primary permission to look at for the external client is going to be "Browse Project", you will want to set up the one project so that the user only has this permission so they can only see the data, but not interact.

However you will also need to set up all the other existing projects in a way that does not grant permissions to any logged in user or a group that the client is part of.

Check out the following KB articles that give a breakdown on restricting project access in this manner for additional details on what to look for:

Regards,
Earl

All comments

Earl McCutcheon

Hi Quinn,

However you will also need to set up all the other existing projects in a way that does not grant permissions to any logged in user or a group that the client is part of.

Check out the following KB articles that give a breakdown on restricting project access in this manner for additional details on what to look for:

Regards,
Earl

quinn_woodridge

Earl,

Thanks for the KB docs. The second one was what I was originally doing, however it still doesn't allow the users in a group assigned to the 'Browse' role to see the sprint or board.

Does the first KB doc allow for external groups to see the whole project including the sprint and board?

Thanks,

Quinn

Edit: It seems that the first KB doc also accomplishes the same task of only giving a user access to the project issues and not active sprints, backlog, or boards.

Earl McCutcheon

Hi Quinn,

For the Board visibility its most likely the board filter share permissions. In conjunction with project permissions to have access to the issues on the board, If the filter is not shared with a user the board is not accessible to that user.

Check out the filter used by the board and refer to "Managing shared filters" for steps to alter the share permissions.

Let me know if the filter shares are the blocker.

Regards,
Earl

quinn_woodridge

Earl,

I have also tried changing around the filters to no avail. Here's what I have in place so far:

The permission scheme is set up so that the 'Client' role only has browsing access and everyone else has edit-ability (internal users).
The clients have their own individual group per project, for example project1-users, project2-users, etc.
The groups for each project do not have any product access but do have site access.
The shared filter is set up so that it is shared with the above mentioned groups and also the clients in the project (ex. the filter says Group: project1-users Project: Project1 Role: Clients).

I will mention that I have only moved two projects onto this new permission scheme where I am trying to get this to work.

In addition, I have tried giving the groups access to Jira Software product which allows them to see the boards, active sprints, etc. however they can now see other projects. Could this be because the other projects are not on the same permission scheme?

Thank you for all of your help,

Quinn

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

board

permission

group

role