It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restricting user to access projects

How to restrict an user from accessing a specific project in JIRA Software?

3 answers

1 vote
Jack Community Leader Sep 18, 2019

You need to remove the user from any group that has permissions to the project. You can do this by creating a new group for the project and exclude them from the group or you can remove them from the group that currently has access to the project. Keep in mind that the later likely will impact them in other projects.

Hi Jack,

We tried as above. But, has impact on all projects. Cannot add user/group permission to a specific project? Is there any other options?

Jack Community Leader Sep 18, 2019

I would refer you to the documentation. Here is one overview article. It is all quite doable just need to be diligent about how you setup permissions for each project as Joe eludes to. By default permissions are pretty open and when users get added to Jira they typically go into a common group, e.g. developers or jira-software-users and that group is given permissions on each project. It would be a challenge for me to guide you w/o really having access to your instance and spending time assessing things.

0 votes
Joe Pitt Community Leader Sep 18, 2019

JIRA permissions

First, by default JIRA has a horrible permission scheme that violates security best practices by allowing everyone that can logon to do just about everything.

JIRA works by GRANTING access. You can't restrict access. By default, it grants access to the group used to logon (see Global permissions to see the "can use" groups and admin groups).  This is where users are getting their access.

  1. The FIRST thing you need to do to get control is to remove any groups with logon privileges from the permission scheme unless you absolutely want everyone to have that permission.
  2. Then I suggest you setup Project Roles for the various functions like, tester, QA, Browse Only, etc.
  3. By using project roles, one permission scheme will cover all projects. The project admin controls project role membership
  4. If the project leads want everyone that can logon access to the project they can add the logon group to a project role with the desired permissions.

This may be a big effort, but it will pay off down the road by making it easy to control access.

Most of the 'old timers' use project roles. It meets the best practice for security and gives complete control to the project lead for access to their project. JIRA comes with many project roles, but you can add more if you have a special need.

The user must not be in any group or role with permission to browse the project.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

302 views 1 3
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you