nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hide Customer Portal for some customers

Bastian Stehmann

Hi,

we have some Service Desk Customer Portals.

Some of them are for specific customers only, others are in general open for all.

For example,

Service Desk A is visible for Customer A

Service Desk B is visible for Customer B

Service Desk C is in general visible for all customers

The configuration, that only customer A can see portal A and customer B can see portal B works without problems.

But A and B can see portal C. That is so far correct, but to make it easier for the customers to select the right portal, we would like to hide portal C for customers from A and B.

I know the Extension for Jira Service Desk Add-On, but that's only whitelisting with jira-groups and we need some kind of blacklisting.

Is this possible somehow?

Accepted answers

Jack Brickey

Hi Bastian, i'm a bit confused. You say you want both customers to see project C and they can but then it seems you don't want this? Are you saying that you want to somehow combine two project for the customers into one?

In other words are you saying customer A goes to the help center and sees a single project that consists for request types spanning two projects. Basically, in this case the customer would only see all request types w/o having to click on a project/container of these request types?

example:

project A:

request 1
request 2
request 3

project B:

request 4
request 5

would appear on customer A's portal as:

request 1
request 2
request 3
request 4
request 5

if this is the case it isn't possible

All comments

Jack Brickey

example:

project A:

request 1
request 2
request 3

project B:

request 4
request 5

would appear on customer A's portal as:

request 1
request 2
request 3
request 4
request 5

if this is the case it isn't possible

Bastian Stehmann

Hi Jack,

Sorry if it was not clear.

Customer A and B can currently see Portal C because it is open for everyone.

But we want that only Customer A and B can not see the portal C nor the request types (just as if it does not exist) but the rest of the world should see it.

So we just want to exclude the customers from Customer A and B but keep it open for everyone else.

Does this make it more clear?

Jack Brickey

ah I see so it is like this today....

customer A and B each have a private project they can see - project A and B. and you also have an open to the public project C that customers A&B can also see because it is public.

Right?

and you want project C to be semi-public in that you want to hide from A & B. Right?

Unfortunately, this is not possible. Public is public and so Customers A&B have access to the Help center they will absolutely have access to C. I ran into this recently and trialed Refined Themes as a possible solution and it would like work in this case but it wasn't exactly what I was looking for so punted. Basically, you need independent help center (root) portals where you could associate projects as desired. I really really wish Atlassian would provide a more powerful portal solutions. I get that public is public but even if I could simply hide it on the screen that would be fine. I could live w/ the situation where the customer could stumble-upon it.

Bastian Stehmann

Ok, thanks for the answer, that's what I expected, but I hoped that there might be a solution.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server