Scoping vs. Restriction Rules in Salesforce

Managing data visibility and access is crucial for maintaining security and ensuring that users can efficiently perform their tasks in Salesforce. Two powerful tools provided by Salesforce to control record visibility are Scoping vs. Restriction Rules. Both rules manage data access in different ways and suit distinct use cases.

This comprehensive guide delves into the nuances of Scoping vs. Restriction Rules, comparing their features, benefits, and ideal applications. By the end of this article, you’ll have a clear understanding of when and how to implement each rule to optimize your Salesforce environment.

What Are Scoping Rules?

Scoping Rules filter the records users see by default based on predefined criteria. They act as a lens through which users view data, allowing them to focus on records that are most relevant to their role or responsibilities.

Key Features of Scoping Rules

Default Record Visibility: Scoping Rules determine which records appear by default in list views, reports, and searches based on criteria like region, role, or ownership.
Dynamic Switching: Users can switch between different predefined scopes to focus on specific sets of records.
No Impact on Security: Scoping Rules do not restrict access; they only refine the default view of records.
Supported Objects: Applicable to custom objects and selected standard objects like Account, Case, Contact, Event, Lead, Opportunity, and Task.
Rule Limits: Enterprise and Developer editions allow up to two active rules per object.

Use Cases for Scoping Rules

Sales Teams: View only their assigned leads or opportunities.
Support Agents: Focus on cases relevant to their region or expertise.
Marketing Teams: Target specific accounts or contacts based on engagement criteria.

Benefits of Scoping Rules

Enhanced Productivity: Reduces noise and unnecessary searches, ensuring users can concentrate on high-priority tasks.
Improved User Experience: Provides a tailored view of records, making it easier for users to find relevant data.
Flexibility: Allows users to adapt their view of records dynamically.

What Are Restriction Rules?

Restriction Rules actively limit user access to specific records based on defined criteria. Unlike Scoping Rules, Restriction Rules enforce security by preventing users from accessing records that do not match the specified conditions.

Key Features of Restriction Rules

Record Access Limitation: Restriction Rules filter out records that fall outside the defined criteria, making them inaccessible to users.
Enhanced Security: Ideal for controlling access to sensitive or confidential information.
Supported Objects: Applicable to custom objects, external objects, contracts, tasks, events, time sheets, and time sheet entries.
Rule Limits: Enterprise and Developer editions allow up to two rules per object; Performance and Unlimited editions allow up to five.

Use Cases for Restriction Rules

Sensitive Data: Prevent unauthorized users from accessing confidential information.
Compliance Requirements: Ensure that only authorized personnel can view certain records.
Data Segmentation: Restrict access to records based on specific criteria like region or department.

Benefits of Restriction Rules

Enhanced Data Security: Protects sensitive information from unauthorized access.
Compliance Assurance: Helps meet regulatory and organizational compliance requirements.
Granular Control: Provides fine-grained control over who can access specific records.

Scoping vs. Restriction Rules – A Comparative Analysis

Feature	Scoping Rules	Restriction Rules
Purpose	Refines default record visibility	Actively limits record access
Impact on Security	No impact; does not restrict access	Restricts access to records
User Control	Users can switch between scopes	Users cannot access restricted records
Supported Objects	Custom objects, Account, Case, Contact, Event, Lead, Opportunity, Task	Custom objects, Contracts, Events, Tasks, Time Sheets, Time Sheet Entries
Rule Limits	Up to 2 active rules per object (Enterprise/Developer editions)	Up to 2 active rules per object (Enterprise/Developer editions); up to 5 in Performance/Unlimited editions
Implementation	Configured via Object Manager	Configured via Setup menu

Implementing Scoping Rules

To implement Scoping Rules in Salesforce:

Navigate to Object Manager: Go to Setup and select the object for which you want to create a Scoping Rule.
Create a New Scoping Rule: Define the user criteria and record criteria that determine which records are visible to users.
Assign the Rule: Assign the Scoping Rule to the appropriate profiles or permission sets.

Note:As of Winter ’22, Scoping Rules can only be created using the Tooling or Metadata APIs. There is no user interface available for creating Scoping Rules.

Implementing Restriction Rules

To implement Restriction Rules in Salesforce:

Navigate to Setup: Go to Setup and search for “Restriction Rules.”
Create a New Restriction Rule: Define the user criteria and record criteria that determine which records are restricted.
Assign the Rule: Assign the Restriction Rule to the appropriate profiles or permission sets.

Note: Restriction Rules are applied to features like list views, reports, lookups, related lists, and search.

Best Practices for Using Scoping and Restriction Rules

Use Scoping Rules for Default Record Visibility: Employ Scoping Rules to refine the records users see by default, enhancing productivity without compromising security.
Use Restriction Rules for Sensitive Data: Implement Restriction Rules to protect sensitive information and ensure compliance with organizational policies.
Avoid Overlapping Rules: Ensure that a given user is not subject to multiple Scoping or Restriction Rules that conflict with each other.
Regularly Review Rules: Periodically review and update Scoping and Restriction Rules to align with changing business requirements and security policies.

FAQs

Q1: Can Scoping Rules and Restriction Rules be used together?

Yes, Scoping Rules and Restriction Rules can be used together to provide a layered approach to data visibility and security. Scoping Rules refine the default view of records, while Restriction Rules enforce access limitations.

Q2: Are Scoping Rules and Restriction Rules available in all Salesforce editions?

Scoping Rules are available in Performance and Unlimited editions, while Restriction Rules are available in all editions. However, the number of active rules per object may vary depending on the edition.

Q3: Can Scoping Rules and Restriction Rules be applied to all objects?

Scoping Rules filter the records users see by default based on predefined criteria. They apply to custom objects and selected standard objects like Account, Case, Contact, Event, Lead, Opportunity, and Task. Restriction Rules limit access to custom objects, contracts, events, tasks, time sheets, and time sheet entries.

Q4: Do Scoping Rules and Restriction Rules affect child records?

Scoping Rules do not automatically restrict access to child records.

Scoping vs. Restriction Rules