Add Row-Level Security with a Data Governance Policy
You must create a role hierarchy to define your sales teams and the data each role can
access before you set up Sales Insights. The following example shows you how policies might be set
up.
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.
Row-Level Security Example based on Record Ownership
This policy ensures that a user can only view records (for example, Opportunities) that they are
explicitly designated as the owner of.
Determine Which Data DMO to Include in the Policy.
The policy must be applied to the primary DMO that contains the record ownership field.
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
Navigate to the Data Governance tab in Data 360 and create a new Data Policy.
Set the Resource to Record.
Select the DMO: ssot__Opportunity__dlm.
Set the Action to Deny. (This is often used to override the default "Allow All" policy,
or you can use an Allow policy that explicitly filters.).
Define the Condition (the security predicate):
Set the rule to Deny access to the record unless the record's owner matches the logged-in
user.
Condition Logic: ssot__Opportunity__dlm.ssot__OwnerId__c Is Not Equal To
$User.ssot__Id__c
Interpretation: If the opportunity owner ID does not match the logged-in user's ID, deny
access to that record.
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.