Playbooks: Need the ability to "lock" the Playbook so it cannot be edited by end users
None
We have run into a situation where CSMs are editing the names of auto-triggered CTAs and/or Tasks, which is impacting some of our Rules and/or Reports that depend on the naming conventions of those items.
We need a way to lock fields on certain Playbooks (CTA Name, Task Subject, Reason, Priority) for CTAs thatwe do not want end users to edit.
We need a way to lock fields on certain Playbooks (CTA Name, Task Subject, Reason, Priority) for CTAs thatwe do not want end users to edit.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
But what I am talking about is once a Playbook gets attached to a CTA....we need the ability to restrict the fields that can be edited for CTAs to which a playbook was attached via a rule or manually. Not all the fields, obviously because they still need to be able to change date, add comments, etc...but I am talking about core fields that should not be changed such as name, priority, type.
In both of these examples, the end user can still edit the CTA Name, Task subject, CTA Reason and Type.
Absolutely vouch for this one - we have also Rules created based on CTA Names and some consequent updates to Salesforce based on some tokens as they are the only way to ensure a relationship between a CTA and a Salesforce Task. Any updates on this one@karl_rumelhart ? Thanks
Hi,
We are planning on having field-level permissions which will enable admins to define which fields can be edited by a group of CSMs. I will run this requirement to the Platform PM and keep this group updated on the status of the project.
Thanks,
Monica
CC:@Kartheek