Row-Level Security Example based on Role Hierarchy
This policy leverages the Salesforce Role Hierarchy to allow managers/supervisors to
view not only their own records but also the records belonging to their subordinates. This
capability uses the specialized hierarchy operator in Data 360.
Required Editions
Available in: Lightning Experience
Available with Sales with Agentforce 1 Edition or Agentforce for Sales Add-on
license in: Enterprise, Performance, and Unlimited Editions.
User Permissions Needed
To manage Data 360:
Data Cloud Architect
To manage Sales Insights:
Sales Insights User permission set
To use Sales Insights:
Tableau Next Limited Consumer
Determine Which Data DMO to Include in the Policy
The policy must be applied to
the DMO being secured, linking its owner field back to the user/role structure.
Determine Which Data DMO to Include in the Policy.
The policy must be applied to the DMO being secured, linking its owner field back to the
user/role structure.
DMO
ssot__Opportunity__dlm
Description
The fact object containing sales opportunity details.
Controlling Field (User Context)
ssot__OwnerId__c (Record Owner ID)
Add Policy/Author
In the Data Governance Policy Builder, create a new Data Policy.
Select the DMO: ssot__Opportunity__dlm.
Set the Action to Allow.
Define the Condition using the hierarchy operator.
Set the rule to Allow access to the record IF the logged-in user is hierarchically above
the record owner in the Role Hierarchy.
Condition Logic (Conceptual Implementation):
ssot__Opportunity__dlm.ssot__OwnerId__c Is Hierarchically Above In $Role
Hierarchy
Interpretation: Deny access to the record if the logged-in user's role is NOT
hierarchically above the record owner's role, thus limiting visibility to the user's role
and all roles above them in the hierarchy.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.