You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
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.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks!
We have found out this was caused by Create Issue permission not being specified properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.