How to Create a Scoping Rule in Salesforce

A sales team can quickly lose focus when every rep sees hundreds or thousands of opportunities in list views, search results, and reports. I have seen this happen in growing Sales Cloud orgs where regional teams work on different pipelines but still need occasional access to company-wide data.

A Scoping Rule solves that usability problem. It gives users a focused default record set without taking away the record access that your sharing model already grants them.

In this guide, I will show you how to create a Scoping Rule in Salesforce using an opportunity-management example, explain how it works, and cover the important limits to check before activating it.

What Is a Scoping Rule in Salesforce?

A Scoping Rule filters the default set of records that Salesforce shows to selected users. It helps people concentrate on records relevant to their job, such as opportunities for their region, cases for their support queue, or leads assigned to their sales territory.

For example, imagine a company with 20 sales representatives across India, the United States, the United Kingdom, and Australia. Each rep has access to company-wide opportunities because of the existing sharing model.

However, most reps only need to work with opportunities from their assigned region every day.

Instead of changing record ownership, role hierarchy, or sharing rules, you can create a Scoping Rule that shows each rep the records that match their area by default.

A Scoping Rule does not remove access to records. Users can still open, search for, and report on records that they can access through Salesforce sharing settings. The rule simply reduces noise in places where users choose to filter by scope.

This makes Scoping Rules very different from Restriction Rules. A Restriction Rule limits record access. A Scoping Rule only narrows the user’s working view.

Salesforce supports Scoping Rules for custom objects and selected standard objects, including Accounts, Cases, Contacts, Leads, Events, Tasks, and Opportunities.

When Should You Create a Scoping Rule in Salesforce?

Use a Scoping Rule when users technically need access to many records but only work with a smaller group of those records every day.

Here are a few practical examples:

• A sales representative should focus on opportunities from their assigned region.
• A support agent should see open cases for their product line first.
• A recruiting team should focus on job applications for their department.
• An HR team should view employee requests for a particular location.
• A project manager should focus on active project records assigned to their delivery unit.
• A large service team should reduce the number of cases shown in searches and reports.

A Scoping Rule works best when your main goal is productivity and cleaner navigation.

If you need to stop users from viewing sensitive records entirely, use your organization-wide defaults, role hierarchy, sharing settings, or a Restriction Rule instead.

Pro Tip: In my experience, Scoping Rules work best after the sharing model is already correct. I never use a Scoping Rule to solve a data-security problem because users can still access records that sharing settings allow them to open.

Scoping Rule vs Sharing Rule vs Restriction Rule

Before you configure a Scoping Rule, understand what each Salesforce security feature does. Choosing the wrong feature creates confusion for users and makes troubleshooting much harder.

If you need help with record access before adding a Scoping Rule, review your existing sharing model and confirm that users can access the right records first. A Scoping Rule should sit on top of a well-designed security model, not replace one.

How to Create a Scoping Rule in Salesforce

Let’s configure a Scoping Rule for a sales organization with regional opportunity teams.

In this example:

• The company has 20 sales representatives.
• Each opportunity has a custom picklist field called Sales Region.
• Sales reps already have access to opportunities across the organization.
• We want users with the India Sales profile to focus on opportunities where Sales Region = India.

The goal is simple: when an India-based sales rep filters by scope, Salesforce should show India opportunities first.

Step 1: Create or Confirm the Record Field

First, make sure the object has a field that identifies which records belong in the user’s scope.

For this example, create a custom field on Opportunity if you do not already have one.

• Go to Setup.
• Open Object Manager.
• Select Opportunity.
• Click Fields & Relationships.
• Select New.
• Choose Picklist as the field type.
• Enter Sales Region as the field label.
• Add values such as India, United States, United Kingdom, Australia, and Canada.
• Save the field.

A custom field stores information that Salesforce does not provide by default. In this example, the Sales Region field tells Salesforce which team should focus on each opportunity.

Make sure your team fills this field consistently. You can use a Validation Rule, Flow, or a controlled data-entry process to prevent blank or incorrect region values.

Step 2: Open Object Manager

Now open the object where you want to create the Scoping Rule.

• Click the gear icon in Salesforce.
• Select Setup.
• In the Quick Find box, enter Object Manager.
• Click Object Manager.
• Search for and select Opportunity.

You can repeat the same process for another supported object, such as Case, Lead, Account, or a custom object.

Step 3: Open Scoping Rules

From the Opportunity setup menu:

• Locate Scoping Rules in the left-side panel.
• Click Scoping Rules.
• Click New Rule.

Salesforce now opens the Scoping Rule configuration page.

Step 4: Enter the Rule Details

Complete the rule information.

The Rule Name helps administrators identify the rule in Setup.

The Full Name is the API name. Salesforce uses it when you work with metadata, deployment tools, or APIs. Keep it clear and stable because changing technical names later can create deployment confusion.

Select Is Active only after you finish reviewing the criteria. During initial testing, I recommend creating the rule first and activating it after you validate it with a test user.

Step 5: Configure User Criteria

The User Criteria decides which users receive the Scoping Rule.

In our example, we want the rule to apply to users in the India sales team. You can target users through user fields or permission-based criteria, depending on your organization’s design.

For a profile-based example, configure the following:

This means Salesforce applies the Scoping Rule only when the logged-in user has the India Sales User profile.

In a larger organization, I prefer using a dedicated user field or a Custom Permission instead of relying only on profiles. Profiles should mainly control baseline access, while permission sets and custom permissions give you more flexibility for role-specific functionality.

For example, you could create a custom checkbox field on the User object named Use India Opportunity Scope. Then you can target users based on that checkbox instead of creating or changing profiles.

Step 6: Configure Record Criteria

The Record Criteria determines which Opportunity records Salesforce includes in the user’s scope.

For this example, configure the criteria like this:

This condition tells Salesforce:

Show opportunity records where the Sales Region field equals India for users who meet the User Criteria.

Keep the criteria simple. Salesforce supports only limited logic in the setup interface. Unless you use API-based options, Scoping Rules support the Equals operator, and the standard setup does not support building complex AND or OR conditions.

If your scope requirement needs multiple values, Salesforce supports comma-separated values in record criteria for IDs or strings. For example, you could include India, Singapore, and United Arab Emirates where the business scenario supports a regional cluster.

Step 7: Save and Activate the Rule

After entering the User Criteria and Record Criteria:

• Review every value carefully.
• Click Save.
• Confirm that Is Active is selected when you are ready to enable it.

Your Scoping Rule is now ready for testing.

Remember that Salesforce allows only one Scoping Rule or Restriction Rule per object for a given user. Make sure two active rules do not evaluate as true for the same user on the same object.

Test the Scoping Rule in Salesforce

Never activate a Scoping Rule across a production team without testing it first.

Create a test user or use a safe test account that matches the User Criteria. Then test the rule in the same way your users work every day.

Test List Views

1. Log in as the test user.
2. Open the Opportunities tab.
3. Select a list view.
4. Open the list view filters.
5. Choose Filter by scope if available.
6. Confirm that Salesforce returns only opportunities where Sales Region equals India.

The user should still be able to access other records they already have access to through sharing settings. The Scoping Rule only changes the focused record set.

Test Reports

Create or open an Opportunity report.

1. Run the report as the test user.
2. Enable Filter by scope where available.
3. Confirm that the report returns only scoped opportunity records.
4. Remove the scope filter and confirm that the user can still access records allowed by the sharing model.

This test proves that your rule improves focus without changing underlying security.

Test Search Behavior

Search behavior can surprise users after you enable Scoping Rules. Ask test users to search for both in-scope and out-of-scope records.

They should find relevant scoped records easily. If they need a record outside their scope, they should understand that they can remove or change the scope instead of assuming the record disappeared.

Things to Keep in Mind

• Scoping Rules do not secure data: Users can still access records allowed by organization-wide defaults, roles, teams, manual sharing, and sharing rules. Use a Restriction Rule or a stronger sharing design for true data protection.
• Use clean field values: Your record criteria depend on accurate values. If Sales Region stays blank or users enter inconsistent text, the rule will exclude records that should appear.
• Avoid overlapping rules: Only one Scoping Rule or Restriction Rule should apply to a user for the same object. Design user criteria so they do not overlap.
• Test with real user scenarios: Test list views, reports, search, related lists, and daily sales processes. A configuration that looks correct in Setup can still confuse users in Lightning Experience.
• Keep criteria simple: The setup-based rule configuration has limited logic support. If your requirement needs many nested conditions, review whether a custom field, Flow, or an API-managed rule will produce a cleaner design.
• Document the business purpose: Add a clear description to your admin documentation. Future admins should know which team uses the rule, which records it scopes, and why the organization created it.

Frequently Asked Questions

Conclusion

A Scoping Rule gives Salesforce users a cleaner, more relevant workspace by filtering records based on clear user and record criteria. Start with one simple use case, test it with realistic users and records, and keep your sharing model separate from your scoping strategy.

You May Also Like

• How to create owner-based sharing rules in Salesforce
• How to create restriction rules in Salesforce
• How to create sharing rules in Salesforce
• How to create a validation rule in Salesforce
• How to create a record-triggered Flow in Salesforce

Bijay Kumar

I am Bijay Kumar, the founder of SalesforceFAQs.com. Having over 10 years of experience working in salesforce technologies for clients across the world (Canada, Australia, United States, United Kingdom, New Zealand, etc.). I am a certified salesforce administrator and expert with experience in developing salesforce applications and projects. My goal is to make it easy for people to learn and use salesforce technologies by providing simple and easy-to-understand solutions. Check out the complete profile on About us.