Why are team members from another project suddenly showing as assignable members of a separate team?

[Yaheli Sage]

Hi all. Another member recently brought to my attention that when assigning issues in our project, a trusted collaborator who is not a part of this project (and in fact, not a part of the organisation at all) who I work with on a separate project is suddenly showing up as a potential assignee for all of our issues. He can also suddenly see and possibly alter our board etc. This is obviously a big issue for us. How did this happen, and how can I fix it? I would like to repeat:

- He is NOT a team member on this project, so I cannot remove him from the team to fix this (yes, I have double and triple checked this)

- However, he SUDDENLY HAS ACCESS to this project

- No one is aware of having done anything which could cause this

- I CANNOT delete either of the projects to fix this issue as both are active

Thank you for any help you can provide!

[Jehan Bhathena · Accepted solution]

Hi @Yaheli Sage ,

Adding to @Nic Brough -Adaptavist- 's answer, if you have the site-admin role, (and if youre using a company-managed Project) you can use the permission helper to check what permissions grant this "trusted collaborator" the permissions that you've mentioned https://support.atlassian.com/jira-cloud-administration/docs/use-the-jira-admin-helper/

Would also suggest check this user's profile to see if he was granted a "jira-admin" access across sites, since that might also allow him/her to override any permission restrictions and make space for their user to gain access.

[Yaheli Sage]

You were right - Thank you!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

This is because one of your admins has added them to the project.  Probably via a role. Or possibly added them to a group that allows access.

Look at the permissions for the project, you will find that this user meets at least one of the access rules.