How can I give an external user access to a specific project on my Jira site only?

Question

I have an external PO for my project and I want to give this person access to 4 projects within my Jira site. I've set up a new project role and added the role to permissions in the permission scheme for my projects.

When adding this person, in the new role, to one of the projects the person also gets access to all shared projects on my Jira site. Is there a way to prevent this from happening? Other than turning off the public access on these other projects on my Jira site. These projects need to be public as everyone in my company needs to be able to access them. But the external user should not be able to access these projects.

Chris Garstin_vrjoe3 · Answer

Has anyone considered implications outside of project permissions?

What about filters and dashboard, which are not confined by project permissions. Simply the name of a filter may expose information a company wants to keep private.

Teams functionality is not permissioned. So an external party could browse teams, and users in your business.

App, Plans, Assets, these are all other areas where information leakage may occur that are outside the scope of project permissions.

Does anyone have real-world experience of allowing third parties into your Jira instance while preventing any information leakage that you don't want exposed?

Prachi Bolar · Answer

Kindly check this for detailed description https://confluence.atlassian.com/display/JIRAKB/How+to+grant+permissions+to+specific+users+in+a+Jira+software+project+that+has+a+shared+permission+scheme

Jack Brickey · Answer

Hi @Samantha Morrison , welcome to the Community.

in a nutshell this is a permissions issue which is likely obvious. One possible reason is that the project that the person wrongly has access to is set to be wide open. For example the permissions include “any logged in user”. I used to do this on some projects when we first started with Jira but soon learned it was a bad idea. I would start by looking at the project the individual has access to, and scour the permissions scheme to see why they may have access. Sometimes the issue is that when a user is added by default, there added into a broad roll, such as jira-users.