Skip to main content
jordan_cook
jordan_cook
Contributor ⭐️⭐️⭐️⭐️⭐️
February 16, 2022
New Idea

Enhanced User Data Permissions and Field-Level Security

  • February 16, 2022
  • 14 replies
  • 551 views

We are using Gainsight NXT. And working in an Enterprise organization, with complex customer relationships and multiple product offerings, we need a better way to limit what Gainsight users can see and do in the platform.

For example, we would like CSMs to be able to view all customers/relationships, but they should only be able to edit the accounts that they are assigned to.

Another example would be to restrict edit access to certain fields, either on the Company object, the Relationship object, or a custom Low-Volume object.

I have heard that field-level security is in the mid-term roadmap, per this post by Preethi George:

Today, some of this can be controlled by virtue of 360 layouts, and data permissions, but that does not scale, and has its own limitations.

    14 replies

    Show previous replies
    Wayne
    Expert ⭐️
    September 11, 2023

    In theory you can achieve this goal with different layouts.

     

    If you have 1 layout where the fields are un editable as your default where everyone gets this one. 

    Then a second layout where they are editable and assign this layout when CSM = current user.

     

    You could also do it based on user role.

     

    Though this is if the fields are attributes/on the Relationship object. If you are talking about any other LV object then yeah this needs to be enhanced.

      Andy Trevino
      Andy Trevino
      Contributor ⭐️⭐️
      February 6, 2024

      I would also like to see field level permissions. I would like to limit particular fields to be edited by leadership only. 

        mmcgowan
        Contributor ⭐️
        February 7, 2024

        Can we get an update as to when this is going to be available?

         

        Thanks

         

        kstim
        kstim
        Helper ⭐️⭐️
        February 7, 2024

        We achieve a basic level of data permissions by using sharing groups and rule-based read/write conditionals. This works for us, but I can see how enhanced field-level permissions would be beneficial for many!

        Terms & ConditionsAccessibility statement