The users prefer to limit their access to the only one project - How to set it up?

Krisztina TEGLASI
Contributor
October 30, 2024

Dear All

The users of the "Z" project can access all projects within the JIRA system. However, since the "Z" project is a team-managed Jira project, the users prefer to limit their access to the "Z" project. What steps should be taken to configure this restriction?

 

Thank you in advance,

Krisztina

2 answers

1 accepted

1 vote
Answer accepted
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 30, 2024

Hi @Krisztina TEGLASI 

I'm probably misunderstanding your question.

There is a project called Z and Jira users can access this project, correct?

See here how to setup Team managed project permissions, manage-how-people-access-your-team-managed-project 

If its the other way around, all project Z members can also see all other projects in the instance

Check all other Jira projects permission schemes on permissions granted  and Team managed projects individually on the permissions set

Krisztina TEGLASI
Contributor
October 30, 2024

Hello Marc,

 

Yes - There is a team-managed project called Z and Jira users can access this project.

The Team-managed project's permissions are OK.

The problem is that "Z' project members can also see all projects in our Jira instance. I've checked other Jira projects permission schemes. 

Screenshot 2024-10-30 134827.png

How to set up individually permissions on the "Z" Team-managed project?

Regards,

Krisztina

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 30, 2024

Hi @Krisztina TEGLASI 

I understand you want to set permissions on the Z project.

A team managed project has open, limited or private option.

They don't have a permission scheme option only company managed projects have.

See doncumentation, next-gen-permissions 

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2024

Hello @Krisztina TEGLASI 

Let me state what I think you're asking.

You have users that have access to one Team Managed project.

You want to prevent them from have visibility to all the other projects in your instance?

Is that correct?

If so, there are two things you have to do.

For all other Team Managed projects you have to ensure that the Access setting for the project is Private, and then in those projects the people who need access to them have to be assigned to Project Roles in them.

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/#Project-access-level

If you have Company Managed projects, those use Permission Schemes. To access a Company Managed project the user must have the Browse Projects permission in the Permission Scheme that applies to that project. Permissions are allocated to users Groups, to Project Roles, and can be allocated to individual Users in Permission Schemes. You need to make sure that the Permission Schemes don't allocate the permission to Public or Any Logged In User, and you need to make sure that the users who should not see those projects are not in the User Groups or Project Roles that have the Browse Permission.

Krisztina TEGLASI
Contributor
October 30, 2024

Hello Trudy,

 

Thank you for the comprehensive response. You have accurately and thoroughly addressed my questions and concerns. I will follow the guidelines provided.

 

Regards,

Krisztina

Suggest an answer

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

Atlassian Community Events