Hi everybody,
we want to deploy Jira for all our users.
I am really new in administration of jira and have some question about the topic.
How can i enforce that a user can only see and _access_ the projects where he / she is member of?
I tried to change the "Browse Projects" Setting in the schema without success to make it unvsibile. Do you have any idea?
Just to know: Is it works as designed, that all users can see all projects? I think about a ceo project for example. In this kind of projects, users should not have the permission to access this project.
Best regards
Sebastian
Hi @Sebastian Lehmann and welcome to the community,
You mention browse projects in a schema, which means you are in a company managed project. You probably created your project from an Atlassian template. These templates do indeed have a default setting that allows browse project access to any logged in user. A consequence of that is what it actually says: anyone who can log into Jira will be able to see that project and all issues within.
If you - rightfully - would like to restrict access to projects, you need to remove any logged in user from the permission scheme attached to your project(s). In the same effort, make sure that you grant access through roles (preferably) or user groups instead.
Alternatively, you could also set up a new permission scheme with restricted permissions just to be used for projects like the CEO project in your example. By doing so, you can still use your current scheme for "open" projects and associate the restricted scheme with projects you would like to expose to a selective audience only.
For more detailed instructions, see this support article on managing project permissions and this detailed description of all project permissions.
Hope this helps!
Hello Sebastian,
Welcome here !!
First, check out 'Browse permission' in the permission with below
* Is that with group
* Is that with 'anyone logged in permission'
* Is that with Role?
It's always best to have Roles to be used in the Permission role (with/without Group). And then the Role member would be overhead of the project admin to manage.
Now, check with the Roles in the global setting, does it has default added any?
Ex. If person AB is not having the browse permission (roles, groups, users) - then they won't be part of the users who CAN'T VIEW THE PROJECT ITSELF'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.