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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,560,622
Community Members
 
Community Events
185
Community Groups

What is the best way to invite external agents to a single project?

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!

3 answers

2 accepted

0 votes
Answer accepted
Veera
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 13, 2020 • edited

@Chris Knowlton 

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.

https://confluence.atlassian.com/cloudkb/how-to-restrict-project-access-for-teams-in-jira-cloud-953142266.html

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 13, 2020

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. 

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. 

Veera
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 15, 2020

You are welcome, @Chris Knowlton

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 15, 2020

:-)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events