This new Restriction Rule feature is the advanced configuration that allows the admins to restrict accessibility for users. All the existing sharing configurations like the OWDs, Sharing Rules and Territory Sharing, etc., are used to extend the user’s accessibility for Objects. The main purpose of the Restriction Rules (Beta) is to control access to a specific set of records for certain users. With our Passbook example, a Restriction Rule can be created on top of the OWD and Sharing Rules in such a way that the only users who require access will be able to see the Passbook records based on the filter criteria set in the Restriction Rules, and other users will be restricted from accessing it.įig 1: Filtering using Restriction Rules (Source: Salesforce Developer Blog) When To Use Restriction Rules? With the Summer ‘21 Release update on Restriction Rules, accessibility can be further controlled on certain objects by restricting the users from accessing non-essential data. In the example, as the Passbook Object is related to Account in a Master-Detail relationship and the OWD for the Account is Public Read/Write, all users would gain access to the Passbook records even when the OWD of Passbook Object is set to private. With those existing features, users with access to a parent object automatically gain access over the child object(s) if they are related in a Master-Detail Relationship. Until Summer ‘21, in order to set the access levels for Objects in Salesforce, we have used the OWDs and Sharing Rules in the org.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |