Add internal Confluence users as Jira Service Desk customers

[Demi Benson]

I'm trying out Jira Service Desk, and working through the (somewhat) helpful Getting Started sections. I've setup JSD as ITIL, as it's for internal users only. I want to get all our users (who have Confluence access) added as JSD customers. We use Google SSO for logins, and SSO login is required to access any part of our site (Confluence, Jira, etc).

I don't want everyone in the world to be able to submit tickets - this is for internal customers only.

I do want everyone in the company to be automatically added as JSD "customers", without having to add them manually. BTW, everyone in the company already has access to Confluence, so my ideal solution would take advantage of that mapping.

How do I do this easily?

[Aaron Williams · Accepted solution]

Hey,

It really depends on whether you have a public instance or not; can I - as a private person - navigate to your https://mycompany.atlassian.com page and view other projects, or do I get forced to log-in with SSO before I view anything

Ours is private and integrated with G-Suite to provision all users; by default no licence is granted but all our employees can view our customer portal after they log-in

https://mycompany.atlassian.net/servicedesk/admin/myproject/customer-permissions

The customer permissions page should help you, you can read more here: link

[Demi Benson]

I updated the original post with "SSO login is required to access any part of our site (Confluence, Jira, etc)."

So, yes, it's private.

The link helped a little bit, but it's out of date - I think I found the correct setting on the "Customer permissions" page, not "Request security".

[Aaron Williams]

That's great, then on the customer permissions page you should make it so that all can open requests and this allows all your provisioned members to see the portal!

The URL I posted with mycompany and myproject just needs to be adapted to your environment to find it again, but you do set this in the Project Settings regardless; if you have another JSD project later you can restrict the portal in this page to hide that project from other users, but it's not a common case to have an open and a closed portal inside the same private instance.