You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
In our company-managed project, members can see and assign users to issues that are not part of that specific projects. That's a pretty big data protection issue in my book. Why is that the standard setting and how/where can i adjust it?
Hi @STX and welcome to the Community!
Check the permission scheme attached to your project, first of all via project settings / permissions. Make sure that browse project / assignable user / ... is not set to any logged in user, as that would effectively make your project accessible to anyone with a Jira license, regardless of who you add to your project on the people tab. If you want to restrict access to a project to a limited set of users, you need to set up a permission scheme where you properly configure permissions using roles. See this support article for more details.
Hope this helps!
Atlassian indeed strongly believes in open work (Research on the benefits of open work) and openness is therefor a default starting point.
When organizations start using Atlassian tools, it is usually not the case that there are suddenly dozens or hundreds of projects, spaces or service desks created and live in production after a couple of days. So adapting (and reusing) the permission schemes to match your company style / culture is not too difficult to accomplish.