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
Next: Root
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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are looking to have 2 external users work on a project with our internal team. What's the best way to invite the 2 external agents so that they only see the 1 project and not the rest of our service desk projects. In testing this the external user I invited could see all projects unless I marked them private, but that only works for next-gen, and is a cumbersome way to set up permissions. What I would like ideally is to be able to assign project permissions to users.
This is a cloud hosted Jira Service Desk with a mix of classic and next-gen projects.
Thanks!
Below KB article explains how you can restrict project permissions to specific users/groups. This is not specific to Jira Service Desk, but applying the project permissions are same for all Jira classic projects.
Hi Chris - Take a look at the Permission Scheme for the projects to see who has Browse Projects permission. I would suggest adjusting that to just use Project Roles and that the project roles are not universally allowing all users to see them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Veera and @John Funk for the information, this was helpful. It looks like this is another reason not to (yet) user next-gen projects, they are not affected by the permission settings the same way classic is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome, @Chris Knowlton
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
:-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.