Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best Practice to Add External Users to Projects

Looking for feedback for the best practice for controlling external access to projects in Jira.

Our goal is to make Jira as secure as possible and confine Client 1 to only Client 1 Projects.

I see two methods of controlling external access to projects in Jira.

Method 1

Create a Group for each Project that has External users called "Project X External Users"

Create a new Permission Scheme for each project that has external users and use the Group created above in the Permission Scheme

Method 2 

Create a Group for each Project that has External users called "Project X External Users"

Use the same Permission Scheme for all projects

On each Project that has an external user use the Group created above and assign to the Roles of the project.


Method 1 seems more overhead of permission schemes, when Method 2 works and I don't see Method 1 as any more secure because in either case the Project lead can add folks to the projects at will.


1 comment

Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 18, 2022

Another option is to create a new role called external users.  Then create a new permission schema with this role to perform the actions you need them to do. This way you don't need an admin to be updating groups. And you can share the configurations per project.



Log in or Sign up to comment