You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to allow access to a team managed project but the user also sees other projects that they should not. I am not sure how to fix this. Do I create a permission scheme for team managed projects or not
Hello @Tracy Miller
Welcome to the Atlassian community.
Team Managed projects (vs. "classic" or Company Managed projects) are available only in the Jira Cloud product. Can you confirm you are using Jira Cloud?
And if you are using Jira Cloud, do you have both Team Managed and Company Managed projects or just one or the other in your instance?
To allow a user to see only one project you have to first make sure that they have the correct permission to see that one project, and then you have to ensure that the access for all other projects is set up so that the user doesn't have permission to those other projects.
The exact method to do this depends on whether you have Team Managed projects or Company Managed projects or both in your environment.
For Team Managed projects the Access setting must be Private in order to prevent unauthorized users from seeing that project. Refer to this for more information:
If you have Company Managed projects then access to those projects is governed by the Browse Projects permission in the Permission Scheme(s) used by those projects. If that permission has been allocated to "Any logged in user", then that makes the project visible to the user. You would have to change the allocation of that permission in each Permission Scheme to ensure that it is not allocated to Any Logged In User, and to ensure that if it is allocated to users groups it is not allocated to any user group where the user you are trying to limit is a member. Permissions in these schemes might also be granted to Project Roles, and Project Roles can be assigned both to individual users and to user groups. So if the Browse Projects permission is allocated to a Project Role, then you have to check the individual projects that use that scheme and examine their roles to see who has been granted that role, and ensure that doesn't include the user you are trying to limit either as an individual or as a member of a user group.