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

Jira Software server version 8, limit user permissions to a single project

Michael_jbdn5r

I'm currently trying JIRA Software and we need to create many projects with many users that may only see and have access to some projects, individually opened for them. The permission schema seems so counterintuitive I can't believe it's that bad, so it must be me...

How can I limit a user's access to a single project, possibly without having to configure multiple project roles, permission schemas and so on?

The ideal solution would be to create a group and allow that group permission to the project, nothing else - but how do I do this?

Thanks!

Accepted answers

Jack Nolddor [Sweet Bananas]

Hi saleweaver,

Project Access is granted by Browse Project permission within the Project Permission Scheme. You can define one project scheme and share it among all existing and newly created projects o create separate Project Permission Schemes for each Jira project.

The best approach is to use a shared project permission scheme among projects and grant this permission to a Projec Role. In that way, Administrators and Project Administrators can manage Role memberships as per project basics. That means every project can have different people within the same Role and as a consequence different people will be able to access to each project.

At first it a bit messy but you can learn how to do it by reading the Permissions made simple for Jira server page

Regards

All comments

Jack Nolddor [Sweet Bananas]

Hi saleweaver,

At first it a bit messy but you can learn how to do it by reading the Permissions made simple for Jira server page

Regards

Michael_jbdn5r

Thanks Jack, but that still means to secure a project, I need to edit the permission scheme for every project to match the role?

Jack Nolddor [Sweet Bananas]

If each project has a different permission scheme you must edit one by one to use either a project role that can be managed by both Jira Administrators and Project Administrators or a group that is enterly managed by Jira Administrators.

That's the point on using Shared Permission Schemes when possible, to reduce these kinds of administration overhead

Regars

Michael_jbdn5r

Ok, thanks again, I get it.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server