Scoping Rules (Beta)

Scoping rules let you control the default records that your users see based on criteria that you select. You can set up scoping rules for different users in your Salesforce org so that they can focus on the records that matter to them. Scoping rules are available for custom objects and the account, case, contact, event, lead, opportunity, and task standard objects. To create, edit, or delete scoping rules, use Tooling or Metadata API.

Available in: Lightning Experience in Performance and Unlimited Editions

This feature is a Beta Service. Customer may opt to try such Beta Service in its sole discretion. Any use of the Beta Service is subject to the applicable Beta Services Terms provided at Agreements and Terms.

Note

For information on enabling the scoping rules beta, visit the Scoping Rules group in the Trailblazer Community. You can also provide feedback and suggestions for scoping rules in this group.

Scoping rules diagram about its relationship with other sharing mechanisms.

When Do I Use Scoping Rules?

Use scoping rules when you want to control the records that your users see by default. A scoping rule doesn’t restrict users’ access to other records they sometimes need.

For example, you have users who support multiple agencies in your org. Each user is assigned to a specific agency each day. You can set up scoping rules so that each morning your users see only the records associated with their specified agency in search results, list views, related lists, and reports. Users don’t need to spend time looking for the correct records, but they still have access to the other agencies’ records if they need them.

Or you have teams of advisors and their support staff spread over multiple offices. Clients can interact with multiple advisors, too, depending on their needs. To support this workflow, you could create scoping rules to allow the support staff to focus on clients of a single advisor, a team of advisors, or an entire office.

How Do Scoping Rules Affect User Access?

Scoping rules are flexible. You can enable and disable them on a query-by-query basis. Plus, they don’t restrict the access that your users have to records. Your users can still open and report on all the records that they can access according to your org’s sharing settings.

Where Are Scoping Rules Applied?

This table shows how scoping rules work with other Salesforce features.

Feature	Description
List Views	Applied in Lightning Experience if Filter by scope is selected
Lookups	Applied in Lightning Experience
Reports	Applied in Lightning Experience if Filter by scope is selected
Search	Applied in Lightning Experience
SOQL	Applied, unless a scope is specified
SOSL	Applied, except for "USING ListView=" clause

In related lists, all associated records that you have access to are visible, regardless of scope.

Note

How Do I Configure Scoping Rules?

Create and manage scoping rules using either the RestrictionRule Tooling API object or Metadata API type. There’s no UI for configuring scoping rules yet.

The RestrictionRule API object is also used to manage restriction rules. For information on restriction rules, see the Restriction Rule Developer Guide.

Note