From an Admin perspective it would be nice to restrict end users from editing some fields in a Low volume object while editing via Data operation or Related list in Customer 360 by making them Read only or not visible in the layout would be really helpful. Currently we need to designate that with the field names. These fields should be updated only by the admin for maintaining data quality.
Page 1 / 1
Hi
Thank you for the feedback
We are working on bringing field-level permissions to Data models. It is currently on our mid term roadmap
Thank you
Preethi
Any update on this? It’s critical for making this a truly useful, adoptable feature.
Current use case for Gitlab:
- LV object holds Instance information, including an Instance ID and Subscription ID that are the combination keys for updates of selected attributes by Rules Engine.
- There is currently one field that they need their TAMs/CSMs updating on a regular basis.
- At the moment, they can change any of the keys used by Rules Engine as upsert IDs by accident or because they are trying to “reparent” to a new subscriptions - leading to multiple records when the rule updates from source data.
Hand in hand with setting fields as editable or not is displaying them on the View popup the way Person view popup works - unable to leave off fields that aren’t relevant to the 1-record view mode.
Let us know - thank you!
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 E-mail address. We'll send you an e-mail with instructions to reset your password.