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
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
I am setting up a project with different organizations and each ORG has its own customer, is there a way to isolate issues visibility from the portal to deny viewing issues out of customer organization?
Simply assuming Service Project A and having ORG 1 with Customer X and ORG 2 with Customer Y
The goal is to get Customer X to view-edit only Requests and issues related to ORG1 and Customer Y to only view-edit Requests and Issues Related to ORG2
If I get it right, once a request is created, you don't want one customer to see other customers' requests. If this is the case, this is how Organizations work in JSM.
When a customer is in an organization all the requests created by that customer are shared with their Organization by default, but not with other Organisations. A customer can even decide not to share a specific request with the Org and keep it private.
If you want to configure it in this way I also suggest you select the "Customers can search for other customers within their organizations" option in the "Customer permissions" configuration of the project, in this way you are also sure that if a Customer tries to share the request with someone they can select only customers from their own Organization.
I hope this is clear and helpful