I intentionally put this question a shocking title for JIRA developers to pay attention This might be a similar one of "On the Service Desk portal page, how do I hide the "Help Center" link from users?" but I'd like to emphasize that this is really so serial problem on utilizing JIRA Service Desk for multiple 'customers'.
Currently, any Service Desk Customers can access the Help Center and browse list of all customer portals for other customers. And furthermore, incredibly, one can create a request in that portal for another customer. We and of course our customers never permit this 'wrong' behaviour and need secure separation of one's own portal from any other customer's. Specifically speaking, we are eager to forbid our Service Desk customer strictly to access contents below:
servicedesk/customer/portal/<number for others>
How can we do this? Or shall we give up JIRA Service Desk and migrate to Zendesk?
did you setup specific project roles for each your project as escribed here https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-users-732528877.html ?
You should be able to give project visibility per customers just defining users to "Service Desk Customers" role per project. Please, take care that your customers are not defined in any group that are associated to "Service Desk Customers" role for other projects.
I performed a test on my instance and if a customer try to access another customer portal he have the following alert :
If a customer does to the list of all service desk projects servicedesk/customer/portals he can see only project in which he has been defined as "Service Desk Customers".
hope this helps,
This has not been solved at all. JIRA Service Desk 7.1.8
Steps to reproduce:
This bug makes this product unusable. We do not want customers to see other projects!
Your referring version number '7.1.8' is one of native JIRA itself, not JIRA Service Desk plugin.
My issue of this case was already resolved and people think this case was closed. Note that my case was an issue on the Atlassian Cloud, not on-premise version.
I think you better raise another item in Atlassian Answers or Support mentioning your JSD version with a bloody title to attract Atlassian's people;-) And I expect a flaw of complaints on JSD's customer portal would move the busiest engineers of Atlassian in the world to improve it.
Any progress made ? Goal is to hide one customer's SD from another by hiding the help center link, while keeping access to the different service desks public. Possible?
Blocking access to each service desk per customer as offered in the Jira Service Desk options would mean syncing all user databases beforehand, not quite handy.
So why not just hide that "help center" link to separate different clients without bothering them to register an account?
Your question seems to imply that you are not restricting access to your portals to users with credentials.
If you refer to https://confluence.atlassian.com/servicedeskcloud/configuring-the-customer-portal-732528918.html and the section on managing access to your portal you will see that there are other options available to you apart from fully open public access.
I believe you could use the second option
to configure for the problem that you are describing.
The place to set your access is described here https://confluence.atlassian.com/servicedeskcloud/managing-access-to-your-service-desk-732528940.html
Hi Fabio and Phill,
Yeah, it seems this shocking title hit;-) Thank you for answering promptly.
Great, that's it, selecting "Only people on my customers list can raise a request" in the Request security setting of each project restrict the Service Desk customer to access the invited projects only.
Then I can continue to use JIRA Service Desk instead of Zendesk:-)
Doing this way you completely loose the ability to raise issues by email.
We have 5 servicedesk projects for 5 different customer companies.
We give 5 different email addresses to raise issues on their projects.
We need to allow users to view issues on the portal but we also need to make a customer from a company not to raise issues on another one project.
So we need to open the creation issues to anyone by email but not to navigate the first level of the customer portal.
Has this been resolved yet? We would like to have an internal vs exernal Service Desk. i do not understand the point of having two portals if both portals are linked together via a help center. I think the correct fix would be to remove the Help Center altogether so we can keep the different Portals seperate. Also we should be able to modify the endpoint urls so that customers cannot guess what other portals are.
Currently you are limited to:
I'm also looking an answer to this and made a similiar question concerning visibility and grouping portals here: https://community.atlassian.com/t5/Jira-Service-Desk-questions/Help-Center-amp-Portals-visibility-and-management/qaq-p/826311
Using: Service Desk Cloud Version
I have successfully figured out how to fully isolate all of our customers from one another in the Help Center. Here's how I did it.
Doing this will now hide this project from the pool of projects in the Help Center. Once I did this for all customers, this meant that there were no projects visible now for my test user.
Next, on the Customers page, add an 'Organization' (pretty much a group of people) to the project (if you don't have one already). Now, any users that you add in this organization will only be able to access to the portal of the project(s) that they are included in.
I really hope this helps someone out there as this has been a customer service nightmare for almost a year now.
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
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