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; } } }

Can Customers tab in Channels & People be hidden from certain user group?

Katarina Puchrikova

Hi,

I'm wondering if there is any possibility to hide the Customers tab in Channels & People be hidden from certain user group? Or at least a way to hide some customers and organizations from a specific user group?

We will have agents from some of our customers with access to the project and we don't want them to see any information about other customers.

Can anyone advise?

Thanks,

Katarina

Accepted answers

Dave Mathijs

Hi @Katarina Puchrikova I do understand your question, but I don't think there's a solution. These sidebar features are an essential part of Jira Service Management and available for all agents.

I think the only workaround would be to create separate service projects, but that may not be feasible either.

All comments

Dave Mathijs

Hi @Katarina Puchrikova I do understand your question, but I don't think there's a solution. These sidebar features are an essential part of Jira Service Management and available for all agents.

I think the only workaround would be to create separate service projects, but that may not be feasible either.

Katarina Puchrikova

Hi @Dave Mathijs thanks for your answer. I've tried the workaround that you suggested and now a new issue appeared. When I create a new issue as an agent from customer B, I can see other customer's project in the dropdown menu for Project field. Can this be somehow configured so the customer agent can not choose nor see other projects?

all projects.png

Dave Mathijs

Remove the agents who are not allowed to see these projects from the Service Project Agent project permission in the permission scheme associated with that project.

It depends whether you work with groups or project roles for this permission. You may need to split the permission scheme if needed.

Katarina Puchrikova

Thanks!

We have found out this was caused by Create Issue permission not being specified properly.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management