In this post, we will learn how we can Enhance Security with Salesforce Restriction Rules. Using this, we can apply filters to determine which record will be visible to the end user, using OWD/Sharing rule combined with Record Criteria.
What is Salesforce Restriction Rules
Restriction rules provide added security for your organization to limit the records that users can access. With Restriction rules, we can prevent users from accessing records that contain sensitive data or information that isn’t needed to end customers.
How do Restriction Rules work?
With Restriction rules, we can make certain records invisible, or unavailable, for certain users. After the restriction rule is applied, certain records fall outside the parameters for what they can access based on Sharing setting.
Configure Restriction Rules in Salesforce
Let’s see how to create Restriction rules. Please follow the below step to do that
- Click on Setup
- Then Click on Object Manager
- From Object Manager Select the Task Object ( You can select which on which you want to create restriction rules)
- Then Click on New Rule button
- Then configure the Salesforce restriction rule as per client requirement.
Restriction Rules considerations and limitations
- Before creating restriction rules, turn off Salesforce Classic for your org if it is on
- Restriction rules are applied to the following Salesforce features.
- List Views
- Lookups
- Related Lists
- Reports
- Search
- SOQL
- SOSL
- Restriction rules are available for custom objects, contracts, tasks, events, time sheets, and time sheet entries.
- At this moment we can create only a maximum of 5 Restriction rules per object.
- And we cannot have AND or OR conditions in the criteria
- Check Salesforce Restriction Rule Considerations guide to learn more.
Summary
Please share your experience with Restriction Rules with us and please subscribe to our youtube to get notifications for our upcoming sessions.
