---
schema_version: "1"
id: c0fed5057380ce2e139521d2832cfbd93c3732eb7a1f89ae9c3a0ba35160c190
title: Create a Scoping Rule
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/security_scoping_rule_create.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.security_scoping_rule_create.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8ff4936951a862d4bb6a943fd33ab1e33a246c82e5d6f9a96737a7a1fc087c4b
description: Determine which records your users see by default. When a scoping rule is applied to a user, the data that the user sees in list views and reports is filtered by the criteria you set.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Create a Scoping Rule

Determine which records your users see by default. When a scoping rule is applied to a user, the data that the user sees in list views and reports is filtered by the criteria you set.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d27530e69">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d27530e69 ">To create and manage scoping rules:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d27530e69 ">Manage Sharing</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d27530e69 ">To view scoping rules:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d27530e69 ">View Setup &amp; Configuration AND View Restriction and Scoping Rules</td>

          </tr>
        </tbody>
      </table>

Scoping rules are available for custom objects, accounts, cases, contacts, events, tasks, leads, and opportunities. You can create up to 2 active scoping rules per object in Developer edition and up to 5 active scoping rules per object in Performance and Unlimited editions.

1. In Object Manager, click the object name for your scoping rule.
2. In the sidebar, click **Scoping Rule**, and then click **New Rule**.
3. Enter the rule’s name and full name. The full name is the name of the component used by the API.
4. To have the rule take effect upon saving, select **Is Active**.
5. Under User Criteria, select which users this scoping rule applies to.
    - If the rule applies to a subset of users such as those in a given role, profile, or department, select **User Criteria**. Then, select the field to use as criteria.
        
        Set the Type field as **Current User** when the rule applies to the currently logged-in user.
    - If the rule applies to a subset of users with a custom permission, select **Permission Criteria**. To filter records for users with the custom permission, set the Boolean value to **True**. To filter records for users who don’t have the custom permission, set the Boolean value to **False**.
6. Under Record Criteria, select which records the specified users see by default. For the Field value, you can reference another object’s field using dot notation.
    
    For picklist values, select a picklist field, and then click **Choose values**. For other field types, to designate more than one value in the record criteria, you can specify a list of comma-separated strings or 15-character IDs in the Value field.
    
    To include a single value that contains a comma, surround the value with double quotes (”).
7. Save the rule.
    
    ![The case object in the Object Manager appears with the Scoping Rules link selected and a rule called Cases Created by Current User shown.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-access-264-0-0-production-enus/a92be132-3cbc-412a-9262-130636120c14/access/images/sharing_create_scoping_rule.png)
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-access-264-0-0-production-enus/a92be132-3cbc-412a-9262-130636120c14/images/icon_note.png)
    
    Note Salesforce doesn’t validate that only one active rule applies for a given user. If you create two active rules, and both rules apply to a given user, only one of the active rules is observed.

After you activate a scoping rule, users select the filter option **Filter by Scope** to update their list view or report filter and focus on a filtered set of records.

#### See Also

- [Enable Custom Permissions in Permission Sets](https://help.salesforce.com/s/articleView?id=platform.perm_sets_custom_perms.htm&release=264.0.0&type=5 "Custom permissions give you a way to provide access to custom processes or apps. After you’ve created a custom permission and associated it with a process or app, you can enable the permission in permission sets.")