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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Provide temporary access to customers

Is there a way or means to provide temporary access to customers, we are looking for a way to add customers to Jira service cloud who are evaluating products but do not have support yet.

 

1 answer

0 votes

Yes, add them as customers, then remove them when you don't need them any more.

I think there's a deeper use-case than you've described here though.  Could you expand on that?  My answer only caters for what you've asked, and I think there's more to it.

So these eval customers would need help regards the product, we may need to open requests answering questions etc. for few weeks to few months. Instead of adding them as customers can they be cc'ed in the request or not.

Ok, but why would they not be customers at this point?  They need the same access as customers as you describe it.

Since not evals could turn into real customers or they may or may not buy the product. At this point they are potential customers.

 I was using "customer" in the sense of Jira account type.

These potential customers need access to your service desk so they can open requests for questions, get responses and so-on.  Which is exactly the same as your real customers usage.

So you might as well add them as (Jira SD) customers, and remove them when you don't need them any more.

You might want to put them in an organisation together so you can identify them, and you might not want them to have access to the same portals as your real customers (until they become one), but that's a matter for the portals, not the account type.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
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...

356 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