Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to manage viewing permissions?

Hardik Sheth
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 18, 2025

I have added different team members to different projects. But the team members can see all the other projects and its details event though they are not in a particular project. How to manage this viewing permissions? The team member should be able to see only those project and details in which they are added as a member.

2 answers

4 votes
Shalini Pradhan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 18, 2025

Hello @Hardik Sheth ,

Good day! Welcome to Atlassian community :) 

  • You need to navigate to your Company managed projects -> Project settings -> Permissions and make sure "Any logged in user" is not added under Browse Project permission
  • You need to navigate to each of your team managed project -> project settings -> Access and make sure Access level is set to private.

Thank you!

0 votes
Mia Tamm
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 18, 2025

Hi @Hardik Sheth 

In Jira Cloud, project visibility is governed by the Browse Projects permission within each project’s permission scheme, so you can lock down who sees which projects by scoping that permission to only the appropriate groups, roles, or users.


Permission schemes are applied per project, and by removing broad access (like “any logged‑in user”) from the Browse Projects permission and granting it only to specific project roles or groups, you ensure that only members of those roles/groups can view the project.

For team‑managed projects, you can simply switch the project’s Access to Private, which hides it from everyone except invited users. Additionally, you can further tighten visibility at the issue level with Issue Security Schemes or by reviewing global/public access settings.

Company‑Managed Projects

  1. Create dedicated groups for each project team and add the right users to those groups.
  2. Go to Settings → Permission Schemes, locate the scheme used by your project, and click Permissions.
  3. Under Browse Projects, remove any overly broad assignments (e.g. “jira‑software‑users” or “anyone”) and add only your specific project role(s) or group(s).
  4. In Project settings → People, confirm that those groups are assigned to the correct project role so they receive Browse (and other) permissions.

Team‑Managed Projects

  1. In the project sidebar, select Project settings → Access → Change project access, and choose Private.
  2. Invite your team members under Project settings → People; only those invited will see the project listed.

Additional Considerations

  • Jira Service Management: Under Project settings → Customer permissions, set Channel Access to Restricted – Only people directly invited to this project can submit requests.
  • Prevent public/anonymous access: Verify in Global permissions that public access is disabled and that Browse users and groups is limited appropriately.
  • Issue‑level security: If you need users to see only their own issues (e.g., assignees/reporters), configure an Issue Security Scheme and apply it to your projects.

When This Isn’t Possible

Users with Jira Administrator or Site Administrator global permissions will always see all projects, regardless of project‑level Browse settings.

— Mia Tamm
from Simpleasyty

Dave Rosenlund _Trundl_
Community Champion
July 18, 2025

@Mia Tamm : Welcome to the Atlassian Community 👋

Please find and review the Atlassian partner rules of engagements available here in a community article. Among other things they require that you obtain your Atlassian partner badge. There are also particular rules about the way your display your  affiliation with the partner company.

You’re off to a good start, but not quite complying with the guidelines.  Better to learn the “rules of the road” early in you’re Atlassian Community journey :) 

Best,

-dave

 

 

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events