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.
Low volume object : Restrict fields that can be edited via Data operation or Related list in Customer 360
None
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.
Hi@prashant_pareek
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:
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!