Restriction Rules in Salesforce - Learn All About It

Restriction rules help to achieve and enhance the security by providing access to specific users, with the help of restriction rules the security issue can be resolved, it just provides the required access to the user so that no other user can access it, so the less number of users the less risk of security. Restriction rules help to prevent sensitive data which may lead to a security breach, it only allows permission to some specific users only. One more important thing to be taken care of is that it is available for custom objects, contracts, events, tasks, timesheets, and timesheet entries and can be configured through the Tooling or Metadata API.

Restriction rules are only available for some specific Editions, these are Enterprise, Performance, Unlimited Editions and Developer Editions also.

Just take one example, take a user who wants to navigate to some specific list view for activity, so the user can only see those records which fulfil the criteria defined for the restriction rules. If any records link to those records which are under restriction rule are now inaccessible, so at that time the user will see an error message. The best part of the restriction rule is that it totally depends on the criteria specified by you only, which means once you created any criteria for the restriction rule, if any user on which this restriction rule is defined, wants to access any data by any access means like org-wide defaults or sharing rules or other sharing mechanisms is filtered by criteria that you specify.

Don't forget to check out: Learn All About Workflow Rules in Salesforce

When to Use Restriction Rules?

When there is a need that only some specific or limited user can see some certain records so at that time you can use restriction rules.
When there is some sensitive or confidential information to be controlled to access then Restriction rules can be used.
Some events, tasks and even Access to contracts are sometimes very difficult to manage to make it private, so restriction rules can help to solve this problem of visibility and it is one of the best ways.

For instance, you have contending outreach groups that can't see each other's exercises, despite the fact that these exercises are on a similar record. With limitation rules, you can ensure that outreach groups see just exercises that have a place with them and are pertinent to their work. Or then again, assuming you offer classified types of assistance to different people, use limitation rules so that main colleague answerable for supporting these people can see related assignments.

Impact of Restriction Rules on Other Sharing Settings

Users gain admittance to records in light of your association-wide defaults and other sharing instruments, like sharing standards or endeavour in an area on the board.

At the point when a limitation rule is applied to a client, the information that they had perused admittance to by means of your sharing settings is further checked to just records matching the recordFilter. This conduct is like the way in which you can channel brings about a rundown view or report, then again, actually, it's super durable. The number of records apparent to the client can fluctuate significantly relying upon the worth that you set in the recordFilter.

Restriction Rules Configuration

Go to setup or even using Tooling API or Metadata API you can create Restriction rules.
There is a limit of 2 per object restriction rule in Enterprise and even in Developer Edition.
You can create up to 5 restrictions for a single object in Performance and Unlimited Editions.

Check out another amazing blog by Kishan here: Control Access to Organization | Salesforce Guide

Where Are Restriction Rules Available?

Restriction rules are available for custom objects, contracts, events, tasks, timesheets, and timesheet entries. These are some Salesforce features on which Restriction rules are applied :