How to restrict Jira Users to only see/update only their assigned projects/work items?

[Soloman Raju Sapisetty]

How to restrict Jira Users to only see/update only their assigned projects/work items?

We want to restrict the users not to see other projects(Spaces) or any other issues in Jira. 
As per suggestions from below support page, we tried and not able to get the expected result.

https://support.atlassian.com/jira/kb/restrict-users-to-only-see-their-assigned-work-items-in-jira-cloud/

Steps followed as above path:

1. While Inviting User, we have given access as App Jira User.

2. After user logs into Jira he is still part of jira-software-users group. 

3. Admin logged and removed User from jira-softwares-users. User profile now changing as Invited instead of active.

4. Once user logged in, he is still be part of above group and able to see all tickets.

[Trudy Claspill]

Hello @Soloman Raju Sapisetty 

Welcome to the Atlassian community.

Something that has been missed in the earlier responses from @Shalini Pradhan and @Aaron Pavez _ServiceRocket_  is ensuring the users do not have access to Team-managed spaces in your instance if you use those. Team-managed spaces use a different permission methodology. Each Team-managed space has a space level Access setting of Open, Limited, or Private. All users who have licensed access to Jira will be able to at least browse Team-managed spaces that have an Access setting of Open or Limited. To hide the Team-managed space from users it must have an Access setting of Private, and then the users that do need access to it must be explicitly added to that space. 

Refer to

https://support.atlassian.com/jira-software-cloud/docs/next-gen-permissions/

[Shalini Pradhan]

Hello @Soloman Raju Sapisetty ,

Good day! Welcome to Atlassian Community. :)

To ensure that users can only view and update specific spaces and workitems, you would need to make use of Permission Schemes, Project Roles, and Issue Security Schemes.

First step: Restrict space/project visibility

• Navigate to space settings → Permissions and update the Permission Scheme.
• Under the Browse Projects permission, remove any broad access such as jira-software-users or authenticated users like Any logged in users etc, and grant access only to specific users, groups, or project roles.This ensures users can only see the spaces they are explicitly added to.

Second step: Use Space Roles for Access Control

• Instead of assigning permissions directly to users or use groups, it is recommended to use Project Roles ( for example: Users, Developers, external users etc).

• You can then assign users to roles via space settings → People, and then grant permissions to these roles in the Permission Scheme.

Third: Control workitem Editing Permissions

• Within the same Permission Scheme, you can configure permissions such as edit Issues to ensure only authorized users can make changes. Only add those space roles who should be able to

Fourth: Restrict Issue-Level Visibility

• If users should only see certain workitems within a space, such as only assigned ones, you can implement an Issue Security Scheme.
• This allows you to define security levels like 'Only Assignee' and restrict workietm visibility accordingly.
  https://support.atlassian.com/jira-cloud-administration/docs/create-a-new-work-item-security-scheme-and-security-levels/

Thank you

[Aaron Pavez _ServiceRocket_]

Hi @Soloman Raju Sapisetty 

There are a couple of things you need to check. first is that any new users invited to Jira will have access to Jira using the default user group.

If you remove it, then the user wont have access ot jira. The group access will allow a user to have access to the apps in that group.

Then you ned to work with the permissions. If you want them to see a project, you need browse permission. Without it, they won't be able to see the space.

The bad thing is the Bug mentioned, when you add the current assignee, for example, to the browse project, then ALL users will inherit those permissions and will be able to see the project. That might be the problem you are facing.

Check the bug

https://jira.atlassian.com/browse/JRACLOUD-80945

Check the workaround

Workaround to restrict issue view to 'Current Assignee' and Browse Project to only a specific group of users:

Or use a security scheme, which is easier.

Regards