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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I be an agent on one Service Desk, and just a collaborator on another? Edited

So I have service desk product access on my account. I want to be an agent in one service desk in our org, and so in that one I am in role Service Desk Team. But in a second service desk, I want to be able to see and comment on issues, but I don't want notifications or to be able to be assigned issues—that is, on this 2nd service desk I want to be as if I was in role Service Desk Team with only a Jira Software license.

Is this possible?

1 answer

1 accepted

1 vote
Answer accepted

Hello @Mike May !

Yes, it is possible to be and Agent on one service desk and a Participant or Collaborator on another.  The project administration section "Users and Roles" is where the definitions governing each are managed. Here's a link to JSD documentation on the topic:

Hope this helps and if so, please consider clicking the "Accept Answer" button so others searching Atlassian Community see the indicator in their search results.  Thanks!


Thanks Larry. The trick is: those docs say to add a user to role "Service Desk Team" to be a collaborator. But if I do that, and I have a service desk license, I become an agent, not a collaborator, on that service desk. How do I get around that?

Jack Community Leader Jul 18, 2019

You can use any role or group to be a collaborator. Try creating a group called JSD Collaborator, add your name and add the group to the browse and comment permissions.  

Like LarryBrock likes this

Thanks Jack. I decided to create a new Agent-as-Collaborator role (Atlassian support's suggestion for resolving this) and added permissions accordingly. Seems to do the trick. 

Like LarryBrock likes this
LarryBrock Community Leader Jul 19, 2019

That's great to hear @Mike May ! - could I trouble you to click "Accept Answer" so others can find this solution?  Thanks!

Thanks for the follow-up @Jack - I got pulled away and just now had the chance to re-engage.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Desk

Calling all Mindville Insight users, we need your help! (there might be swag involved)

Hello Insight users,  As part of our (Mindville's) acquisition by Atlassian, our training team is looking to build some new Insight training materials and we want to hear from you!  ...

276 views 4 6
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you