Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Sharing customer accounts in JSM Edited


I have the following use case: a support team would like to handle requests from their external client via their internal JSM instance. The client would like to create a single customer account that the client's team would be sharing instead of creating dedicated customer accounts for each team member. I was looking for information on whether such activity would be compliant with the JSM account management policy, but didn't find a definitive answer. Please advise.


2 answers

2 accepted

0 votes
Answer accepted
Jack Community Leader Jun 08, 2021

I would not approach that problem in that manner. If you share a single user account then you really don’t know who open the ticket. JSM is designed such that you can create an organization and add all the individual customers which are free and allow them to open their own tickets. In this manner you can track or accurately the customers issues.

Good point @Jack, thanks! Still :) do you know whether customer account sharing is even allowed?

Jack Community Leader Jun 08, 2021

Well sure you could create a single user and tell everybody what the user ID and password is there’s nothing to prevent you from doing that. The Question is who will receive the notifications sent by Jira?

Fair enough. Once again, thanks for your insight!

0 votes
Answer accepted
Daniel Ebers Community Leader Jun 12, 2021

Depending on how large the client's team is this looks like a challenge to change the password for the role account. They would have to do it as soon a team member quits.
I agree with Jack - it would be better, not just for security reasons, to use the functionality like it was designed with JSM.

There is some further reading available with Atlassian, just in case you want to have a look:

Thanks @Daniel Ebers! Yes, I agree that such an approach could cause security issues. That settles it :). Cheers!

Suggest an answer

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

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

330 views 9 7
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