How to restrict access to an individual Kanban board within a project that has multiple Kanbans

[Rachel Southard]

Hello,

One of my company's departments has three individual Kanban Boards set-up within a single project.  I need to limit access for a third-party contractor to "view only" in only one of the three boards...is this possible?  

Insight is appreciated! 

[Jack Brickey]

@Rachel Southard, I may be missing something in the details here so please let me k ow if my answer is in sufficient. 

Each Kanban board is independent of others and as such you control the shares of each independently. Simply go to Board settings > General and edit the Shares. 

[Rachel Southard]

Thanks, Jack! Unfortunately with the new UI under "General" there is no edit shares option--the only place I'm seeing to control who has access is at the project level which doesn't work when there's three boards within the project.

Any other ideas is appreciated! 

[Jack Brickey]

hmmm... are you on cloud or server? Are you working w/ Kanban boards you created or the default one that comes w/ the project? Here is a view of one of my kanban boards General view and I'm certainly on the new UI. Now are a system admin or the board creator? Can you share an image of what you see?

[Rachel Southard]

That is unfortunately not what I'm seeing--it's a locked group.  This Project and Board were set-up by a former contractor and when that ended, I was told to take over.

When in admin, and in the overall project, you can add people with a label (also pictured), but even when selecting "vendor" it provides access to everything in the project, not just the board.

[Jack Brickey]

you need to take ownership of the boards. Shelby created the boards and is the owner. I recommend you simply create new boards using the same filter. if the filter is shared, which it should be, they you can simply create a new kanban using that filter. Or you can click "Edit Filter Query" and save the filter under a new name so then you own the filter. Then create a kanban using that filter. Try this w/ one of the boards and then simply set it up like the current one or how you would like it to be. Once it all looks good delete the old board and direct everyone to the new one. Repeat for all boards that Shelby owned.

hope this make sense.

[Rachel Southard]

Thank you so much--I'll give it a shot! 

[Paiton Swaim]

Hi there! 

I know this was quite some time ago but when going through something similar on my instance, I ran into an issue where the individual could still see all of the issues on the side bar on the left hand side. Limiting boards did not limit issue access/view. 

One caveat - it was not a perfect test when we tested this so there is a chance that someone had too much permission on the project in general but wanted to pose the question here. 

Any thoughts here? 

[Julian Governale]

In this case, Issue-level security needs to be used.  The boards are just visualization of the issues in the projects so you can limit the audience of a board, but they can still search for the issues. 

Issue-level security allows you to limit what issues can be seen by specific people, roles, groups etc. 

Configure issue security schemes | Atlassian Support