Hi!
We are using Organisations to limit access to different JSM tickets, however, I need to be able to disallow customers from editing this field. Is this possible?
Hi @Jimmy Tracey , the first thing to do is to set up Customer Permissions to best align with you project.
Note that customers can only see/share within the Organization(s) they belong to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So what exactly is your share goal? What do you want customers to be able to share and what do you want to prevent? If you want to prevent sharing then you need to not use Organizations. How are you using Organizations today if not to silo customer sharing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need to prevent customers from being able to add new organisations, and remove organisations from tickets
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using Organisations to silo tickets, but need to remove ability for JSM customers to edit access to tickets. This field should only be editable by Service Agents or ideally just Administrators.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Customers should not be able to add new organizations via the portal share button. Are you finding differently? Only administrators or agents? If so, configured or allowed to add organizations. Customers can only find existing organizations if they are a member of those organizations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Jack, currently our customers are able to remove organisations from tickets this is what we're trying to avoid, but not sure how to lock down this permission
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Indeed if the customer is the reporter they can choose whom to share with and this includes removing shares. This cannot be revoked/changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In our case a customer was able to remove shares even if they werent the reporter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I didn't think that was the case but TBH I have never tested that. Thanks for clarifying. I guess the way Share is designed is such that it is a 'customer' focused field not agent focused. It allows customers to decide what the wish to share.
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.