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; } } }

How do you prevent people accessing specific projects?

Matt Fazakerley

Hi,

Previously all users in our Jira software were working on the same project. Now I am about to set up a second project within the Jira software with a different group of people working on it to the first project. I have been asked to set up the permission settings so that only people working on each project can access the board for their project but I struggling to work out which type of permission settings can do this. Is it Groups, User roles or Permission Schemes? Can any provide guidance to setting up the restricted access?

Thanks.

Accepted answers

Nic Brough -Adaptavist-

It's all of those things, potentially.

You can't restrict people in Jira, the permissions are totally permissive. To hide a project from someone, you have to remove their access to it.

Start with the permission scheme for the project and look at the "browse" permissions - those define who can see a project, You may find lines in there saying "group = X", "role = Y" or even "any logged in user" - kill off the rule that is letting your users in (obviously, making sure the project users are still included)

All comments

Nic Brough -Adaptavist-

It's all of those things, potentially.

You can't restrict people in Jira, the permissions are totally permissive. To hide a project from someone, you have to remove their access to it.

Matt Fazakerley

Hi Nic,

Thanks for your quick reply. I've found that both projects are using 'Default software scheme'. Does that mean that they need to have different schemes first before I can make their permissions different?

Screenshot 2021-03-30 165611.png

Nic Brough -Adaptavist-

Yes, you're absolutely right. If you want different permissions for different projects, you'll need a new scheme to associate with the protected project(s)

You can do them from scratch, but I prefer copying an existing one and then tweaking it.

Matt Fazakerley

Great, I've now copied the scheme and allocated the new scheme to my project.

In the Browse Projects section, does the 'Application Access -Any logged in user' part make the Project role section useless in this case? Or are the both needed?

Screenshot 2021-03-30 170806.png

My thought is to remove the 'Any logged in user' part and create a Group with the people in that will need access? Is that the best way?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud