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

Creating the Service Desk Customer role on Next-Gen for provisioning with Atlassian Access

The new Jira Service Desk Next-Gen project type comes as the simplified solution for easy to start and use for your help desks, without needing a Jira administrator.

One of the differences in comparison with the classic project type is that customer permissions should be managed only on the Customers tab, leaving the internal project access area for internal use only, which makes sense.

Recently, I've worked together with a customer who wanted to leverage Atlassian Access's user provisioning to automate the access grant for portal-only users of their company, these users have Atlassian accounts, so that's feasible.

On classic projects, you just need to use a provisioned group and grant it the Service Desk Customer project role within your Service Desk project, but as things are different for Next-Gen, this role does not exist, where to now?

In order to solve this problem, I went through a round of testings with the new simplified permissions for Next-Gen and got the result that allowed internal users to become customers on Next-Gen projects through Group assignment (Which can happen through user provisioning):

Create a new role, let's name it Service Desk Customer and then grant it the following permissions:

Work on "<Service Desk Name>" requests

Act as an agent and communicate with customers to create, edit, assign, transition, link, and log work on any "<Service Desk Name>" request.

  •  Assign any request
    Add someone to or modify the assignee field on any "<Service Desk Name>" request.
  •  Edit any request
    Change the summary, description, and update custom fields on any "<Service Desk Name>" request.

 Create requests internally

Create "<Service Desk Name>" requests internally and fill out their fields upon creation. 

Collaborate on "<Service Desk Name>" requests

Leave internal notes and attach files to any "<Service Desk Name>" request.

  •  Add attachments
    Add attachments to any "<Service Desk Name>" request.
  •  Add internal notes
    Leave internal notes on any "<Service Desk Name>k" request. 

Explaining the permissions

  • The Assign any request is granted so that customers can create tickets on the portal, even for issues starting as unassigned.
  • The Edit any request is granted so that customers can share the issue with other customers or internal users on the portal.
  • The Create requests internally is the initial permission to allow to use the portal, dependent on Assign any request.
  • The Add attachments and Add internal notes allows to upload attachments and add comments on the portal.
  • Though some of the permissions says "internal", they work for the portal as well.

Test results

The users provisioned into the servicedesk-customer provisioning group created were granted customer access to the portal, without issues to raise tickets, share them, transition them to support through comments (With the proper automation in place), seems pretty good.

I wanted to share this as it might help other people and also detect any outstanding missing permissions in case of different Service Desk Next-Gen project configurations.


Do you need automation to make this work and can that be the outline role and permissions needed alone to accomplish this?

Rodrigo B. Atlassian Team Mar 27, 2021

No need for automations, the permissions above should be sufficient, but share any challenges you had when applying the instructions!

Like Aaron Geister likes this

@Rodrigo B.  Very good work here. I love this, and its very helpful as we transition to the next step of Atlassian to be able to carry our older settings as we are used to those from the classic projects.

Keep up the good works.

Like Rodrigo B. likes this
Rodrigo B. Atlassian Team Apr 07, 2021

Thank you for the kind words, Aaron! It makes me happy to know that my article helped you, I will keep it up!


Log in or Sign up to comment
Community showcase
Published in Jira Service Management

Coming Soon: Insight Changing to Assets

The 2020 acquisition of Mindville added powerful asset and configuration management capabilities to Jira Service Management in the form of Insight. Following the completion of that integration, custo...

228 views 1 9
Read article

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