Row-Level Security Example Based on Manager Hierarchy
This policy is used in organizations where reporting structure is managed by a specific
Manager field rather than the formal Role Hierarchy. This also relies on the specialized hierarchy
operator.
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. This policy is best applied to fact DMOs
that link records to an Owner or User ID.
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 against the Manager structure: Set the
rule to Allow access to the opportunity record IF the logged-in user is hierarchically above
the opportunity owner (based on the Manager field of the user profile).
Condition Logic (Conceptual Implementation):
ssot__Opportunity__dlm.ssot__OwnerId__c Is Hierarchically Above In
$User.ManagerId
Interpretation: Deny access to the opportunity record if the logged-in user isn’t the
manager (or a manager above) of the opportunity owner.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
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.