How do I restrict users to just a single Jira project

[James DonFrancesco]

I only have 5 or so Jira projects. I have 2 other users, and myself as Admin. I don't want the two regular users to access any Jira projects except for the one project they're on.

I can't figure out how to do this, despite the overwhelming documentation.

[Thomas B]

Hey James,

There is a couple ways to achieve visibility of projects in JIRA, but this is how I did it. 

1. Create a group and name it something meaningful by going to Settings > User Management > Groups and Add Group. Place your users and yourself in this group
2. Create a Permission Scheme by going to Settings > Issues > Permission scheme and create a new scheme
3. You can then click on Permissions under the Actions tab of that scheme you just created
4. Give your group access to whatever features you want them to access. I give my users access to everything EXCEPT the following: Administer Projects, Manage Sprints, Move Issues and Schedule Issues.
5. You can then go into your projects and associate this new permission scheme by going to your Project > Project Settings > Permissions > Actions and select "Use a different scheme"
6. Select the scheme you just created

This will associate that group with the projects that you choose. You may have to create another permission scheme for an admin group and associate that with the projects that you don't want others to see. 

A simpler solution you might choose to do is follow the steps I listed above but instead of assigning your regular users, you could also assign everything to the admins and associate that with the projects you don't want anyone else to see.

As your team grows, you may find it beneficial to have an admins group with its own permissions scheme AND a regular users group with its own permissions scheme. I have many projects with many different groups associated with different permission schemes and projects. 

If you have any questions, I'll try to help and I do hope you find this helpful. 

Thomas

[Tomasz Osik]

Hi,

I'm sorry for duplicating question. However, would it be possible to restrict access from user perspective? I have lots of project on jira and just few external people. Going through all project will take "bazyllion" years and this is time i dont really have :(. I would appreciate help :)

Best Regards

Tomasz

[IsaacTest]

But ran into this restriction:

"It is a next-gen project. You can not assign a new permission scheme for next-gen projects. You should create a classic project."

https://community.atlassian.com/t5/Jira-questions/Can-not-associate-a-new-Permission-Scheme-to-a-Project/qaq-p/919156

So how it could be done with new or next-gen projects?

[Tomasz Osik]

Hi,

Would it be possible to restrict access from user perspective? I have lots of project on jira and just few external people. Going through all project will take "bazyllion" years and this is time i dont really have :(. I would appreciate help :)

[Varsha Mungale]

Hi Tomasz, 
Did you find a solution for this problem. I have the same problem. 
I want to restrict 5 people from accessing "any" project except the one the are supposed to work on and on which they need to have all permissions - basically create issue is required. 
And i do not want to change anything with all the other projects that use the default permission scheme. For the same reason - it will take up too much time. 

I followed the steps 1 to 6 suggested by James above in this thread, but that has not worked. I need to enable Browse project access and then these 5 outsiders get to see all the projects. 

Any suggestion is appreciated. 
Thanks in advance 

[Tomasz Osik]

Hi Varsha, 

Kind of workaround it. Took some time but...

I have created, as i called it, "NDA Permission schema". Where only certain group can browse. Then i have created new roles. In global permission i have set what these roles can and cannot do. Then i have changed crucial project security schema to NDA and set up roles in project. Browse and some extra, such as dev, BA etc. This has enabled me to restrict some users from accesing other projects. 

So in essence you are controling access through project roles and not permission schema. 

Please note that i have replaced Browse permission in "Default Permission Scheme" as per screenshot. Just few groups have access to all projects.

Additionally i have set up extra issue security schema to make sure no one will access certain work items

This did allowed me to share some projects to people. 

More less, it works :D 

Hope that helps a bit. Please let me know if you have some questions. 

[Varsha Mungale]

Thanks a lot. Takes time to set up all these roles. And then ensuring that all existing users are not impacted will need some testing. Will get back to you if i get stuck, Thanks

[Tomasz Osik]

If you have sandbox environment, try there. You will double effort but will not affect live users :)

[somethingblue]

Hi James,

You would probably want to create a new permission scheme and associate it to your project.  The Browse Project permission is what you're going to need to focus on.

You can then switch your project(s) to use the copy as you are working on it to test how the permissions will affect the user access.  In addition take a look at the video titled How-to: Set and manage project permissions.

You will end up taking away permissions from both projects and then gradually let people back in but this should resolve your issue.

Cheers,

Branden

[yogananda]

Hello Branden,

As you mentioned above when we click on the link, We cant see the Video titled " How-to: Set and manage project permissions"