adding user without being able to access or view other department projects

[Noria Almeaili]

we need to add a new user from Operations Department to Jira, without him being able to access or view IT department projects/tasks/information/etc.

[Trudy Claspill]

Hello @Noria Almeaili 

Adding to what the others have said, there is a clarification I want to make about Team Managed projects.

Team Managed projects have a project-level Access setting which can be Open, Limited, or Private.

All licensed users will be able to at least see the contents of Team Managed projects that have an Access setting of Open or Limited. If you have Team Managed projects that this user should not be able to see, the project Access setting on each of them needs to be changed to Private, and then the people that do need access to that project have to be explicitly added to the project. 

Refer to:

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

[Staffan Redelius]

Hi @Noria Almeaili 

As @Jack Brickey describes this is handled by group memberships for Company managed projects and by Access list in Team managed projects.

Depending on how your site is configured this can be easy to more advanced. I will describe how to set this up for Company managed projects.

1. Start by checking your permission schema(s) for your project(s). The permission you need to even see a specific project is "browse projects" permission this is normally given given by the standard group "jira-software-user".
2. Create a copy of the permission schema and apply this to the project you want to give access to.
3. Create a new group called i.e "Operations-jira-users" and add the user to that group and remove him/her from the standard group. This group needs to provide application access to Jira.
4. Go to Global permissions and give "Operations-jira-users" permission to browse "Users and groups".
5. Give the group "Operations-jira-users" "browse permissions" in the permission schema for the projects they need access to. OR you can add browse permission to the Space Role "Project member" if you want the project administrators to manage access to the Spaces in Jira. 

This way your current users will have access to the projects like before but the users belonging to the new group will only have access to the project(s) that have the new permission schema.

Note:

As Jack describes above, filters that is shared with "My organization" or actions in the permission schema that have the permission "Any logged in user" will be accessible for the user in your newly created group when given access to the project.

For team managed projects you need to add give users access to the project via the access list.

Best regards,
/Staffan

[Jack Brickey]

Hi @Noria Almeaili , this is managed thru permissions/access settings. It is difficult to give you exact instructions without actually accessing your instance which isn't possible. If your IT project(s) are team managed then it is a simple matter of ensuring that the added user is not in the allowed Access list for that project. If you are using company managed project for IT then review the Permissions and ensure that the added user is not in any group/role that would give them access. Note if your IT project were to use "Any logged in user" then that would allow, well, any logged in user to access.