How do I restrict a user so that they can only access one project?
Asked by Darby Kim:

In my case, I would like my client to only be able to be a member in one of my Jira projects. At times there are issues from other projects that are linked to the issues in the board they have access to. How can I restrict their ability to access the issues in other projects so that they can only view/edit the issues in this one project they were given access to.


Answers:
author: Trudy Claspill
body: Hello [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921)

Adding to the information provided by [@Victor Law](/t5/user/viewprofilepage/user-id/391946) and [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) :

Permission Schemes apply only to Company Managed projects.

Are you trying to grant permissions to one Company Managed project or one Team Managed project?

Do you have Team Managed projects on your instance that you don't want the user to be able to access.

What has been said about Permission Schemes for Company Managed projects is valid. However, in addition you have to consider if Team Managed projects are in use in your environment.

Team Managed projects don't use the Permission Schemes. Instead each Team Managed project has its own Access setting. So, you need to check the Access setting for each Team Managed project to ensure it is set in a manner that doesn't allow the user to access that project.

<https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/>

comments: author: Darby Kim
body: [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) yes I am working with team managed projects. I know that I can add/change people's access to the project in project settings but what I need is for an external client to not be able to view any of our other projects aside from the one that I give them access to. Is this possible?


author: Trudy Claspill
body: Yes. You have to apply the information we've provided in our Answers.

To prevent the user from seeing any other Team Managed project the Access settings on those other projects need to be **Private** . If the setting is **Open** or **Limited** anybody that can access your Jira instance will be able to the see the content of those projects.

If you also have Company Managed projects in your environment, the user's ability to see those depends on the Permission Schemes associated to those projects.

<https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/>

Visibility of those projects is managed by the Browse Projects permission in the Permission Scheme assigned to the project. The Permission can be granted to User Groups, to members of Project Roles, to Any Logged In User, to Public, etc. You would have to check the Permission Schemes used in the Company Managed project to see if any of them grant the permission in a manner that would enable the user to see the project content. To prevent them from seeing the product you may have to change the Permission Scheme.

Permission Schemes for Company Managed projects and the Access settings for Team Managed projects are designed to **grant** permissions, not **deny** permissions. You have to adjust them in a manner so that permissions is not **granted** to the user either directly or indirectly. It is not possible to modify them to explicitly **deny** access; i.e. there is no method to configure the project permissions to say "don't let user X see this".


author: Mikael Sandberg
body: Hi [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921),

Welcome to Atlassian Community!

Permission scheme is what will do this for you. You would have to modify the existing one that your projects are using and limit who can browse the project at least. I would recommend that you use a project role instead of a group, that way you can control who have access to a project from within it. If you use a group then only Jira admins can add/remove users from the group, and you could end up with multiple groups to maintain if some projects do not want to give access to all the users in a single group.

Have a look at this [KB](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/) for more information about permission schemes.


author: Victor Law
body: HI [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921)

It would require reviewing the permission schemes on the other projects, as some projects in Jira might allow any logged-in users to browse or edit.

Hence, I would strongly recommend not only granting a user access to a project but also reviewing whether there are any projects that are publicly accessible within the Jira instance.

Thank you.


Tags: cloud

jira-cloud