Scoping Rules and Restriction Rules

In Salesforce, Scoping Rules and Restriction Rules play pivotal roles in governing user access and data visibility within the platform. Scoping rules primarily define the scope of data that users can access based on predetermined criteria, ensuring that sensitive information is restricted only to authorized individuals or roles. On the other hand, Restriction Rules establish limitations or constraints on particular functionalities or actions within Salesforce, dictating what certain users or groups are permitted to do or access. These rules serve as crucial components in maintaining data integrity, security, and adherence to compliance standards across the Salesforce ecosystem.

Scoping Rules

Scoping Rules enhances your users’ productivity by reducing noise and unnecessary searches. It is a Beta service that let you control the default records that your users see based on criteria that you select. Scoping rules do not restrict the record access that your users already have. Your users can still use all records that they have access to.

Available in: Lightning Experience in Performance and Unlimited editions.

Does Scoping Rules Affect User Access?

Scoping rules allows you to enable and disable them on a query-by-query basis and they don’t even restrict the access that your users have to records.

How Scoping Rules works with Salesforce feature?

How Scoping Rules are configured?

Scoping Rules are created and managed by using either Restriction Rule Tooling API object or Metadata API type. There’s no UI for configuring scoping rules yet.

Restriction Rules:

Restriction rules enhance security by allowing certain users to access only specified records. Restriction Rules permits the users to see only the records necessary to them that helps in securing the data and increasing the productivity.

Available in: Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions.

Do other Sharing settings get affected by Restriction Rules?

Yes, other sharing settings get affected after applying restriction rules. When a restriction rule is applied to a user, the data that they had read access to via your sharing settings is further scoped to only records matching the recordFilter.

How Restriction Rules are configured?

Restriction Rules are created and managed in Setup or using Tooling API or Metadata API. There is a limit to create restriction rules per object which is up to two in Enterprise and Developer Editions and up to five in Performance and Unlimited Editions.