projects visibility to users

[Alexandros]

Hello.

I would like to hide projects from certain users. What I could manage is to prevent access from users to specific projects (from project settings->permissions), but those users can still see all the projects in dashboard when they go to Jira Software->Projects.

My problem is that userA should see projectA, but he should not even be aware of the existence of projectB. How can I make projectB completely disappear for userA?

[Petter Gonçalves · Accepted solution]

Hello @Alexandros

Welcome to Atlassian Community!

The behavior you are facing where the user can see the project under Jira Software -> Projects although they can't access it, usually is caused by one of two reasons:

1 - He is added with the global permission to administer Jira, as explained in the documentation below:

- Managing global permissions 

To check if the user is added with that permission, go Jira settings > System > Global Permissions and check if he is added to any of the groups in the Administer Jira permission, configuring it properly in the user management of your site.

2 - A possible bug or permission is configured in a way that allows the user to see the project, although they cannot access it.

To further investigate it, we will need a screenshot of the browse projects permission configured for your Project.

Let us know if you have any questions.

[Alexandros]

Hello Petter.

Thank you for the responce. It was useful.

I describe the solution in order for this thread to be beneficial for other members. The project settings->permissions setting is global, even if it is under a specific project. In there someone can find the groups that can browse projects (which was the area of my interest). But the key was to go to Project settings->People, from where we can manage who can browse the specific project. It is simple after all, but this "permission" setting is confusing to be under a specific project's settings and being global at the same time.

Petter if I got something wrong or missed something, you are most welcome to let me know.

[Petter Gonçalves]

hello @Alexandros

Thank you so much for the provided details. I'm glad to know you were able to solve your issue.

I just would like to clarify one point about the following phrase:

The project settings->permissions setting is global, even if it is under a specific project.

Actually, the permissions under Project settings > Permissions are applied to a permission scheme, which can be global (Applied to all your projects) or not, depending on what projects you configured with that permission scheme.

Indeed, if all your projects are added to the same permission scheme (Which is the default behavior when using just Jira Software application), the groups added with any permissions under Project settings > Permissions will be applied to all projects in your site, that's why you must configure Roles under project settings > People.

I see you've already figured out the most efficient way to work with permissions, but these would be the steps:

1 - Configure the permission scheme (Under Project settings > Permissions) related to your Projects with project roles.

2 - For each Project, add the related users and groups to the roles as you need.

That being said, we understand how confusing and complex these settings can be for new users of Jira, that's why we created the following documentation to better clarify it:

Managing project permissions 

Let us know if you have any further questions. 

[Alexandros]

Hello @Petter Gonçalves , I am new in deed, but excited on the other hand, spending hours the past few daysto learn this great tool!

One new question arrised today is that userA who can browse only projectA (UFO blue icon) created an issue. But even though he cannot browse the other projects, he can select to create issues for those projects! How can I suspend this user to create issue only for the UFO project?

Thanks in advance.

[Petter Gonçalves]

Hey @Alexandros

There is a create issue permission under Project settings > Permissions. You must perform the same restriction you did with the browser projects permission, adding it with the correct roles and adding the user with that role only in the project you want him to create issues.

P.S: Make sure to remove the Application access (Any logged in user) role from that specific permission.

[Alexandros]

Yes I have seen that already, but I assumed that again it is a global setting, unless I create my own scheme as you suggested. I will try it out and let you know.