Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Give restriction to external user.

nortvis-admin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 11, 2023

Hi all,

We want to restrict the users, such a way that they will only able to see a particular project. Other projects are not visible for them.

1 answer

1 vote
Walter Buggenhout
Community Champion
June 11, 2023

Hi @nortvis-admin and welcome to the Community!

In order to do so, you may want to review the permission settings on all projects across your Jira instance. In order to restrict access globally, you need to implement a best practice that facilitates this across the board.

Jira Software supports 2 types of projects: team managed and company managed. That is important as both types handle permissions differently.

In a team managed project, permissions are set for each project individually. And so, if you have any of these already, you will need to review the permission settings of every individual project. This support article describes how to configure access to team managed projects. Basically, you should make sure that you don't have any projects anymore that are configured with open access.

Company managed projects use permission schemes to configure much more granular permissions. Check out this support article to learn more about permissions in company managed projects. Over here, the key permission that determines user access is the browse project permission. Out of the box, default permission schemes grant this permission to any logged in user. That means that every user with a license to Jira Software will be able to access each project. This is what you need to review and adjust for every permission scheme that is linked to a project that you want to restrict.

A small but important side note: be careful when you start modifying these permissions. If you have not changed your permissions before, removing any logged in user from the existing permission schemes may very well lock out many existing users as well. It is important to assess who should be able to access each project and make sure you properly configure access before removing the any logged in user permission.

As a best practice, use roles (developer, administrator, viewer, ...) in your permission schemes and assign people to these roles in each project from the Projects Settings > People tab, preferably using groups over individual users.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events