Scoping Rules Developer Guide
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Scoping Rules
Considerations for Scoping Rules
Display a Branch Location’s Records by Default
Display a Department’s Records by Default
Display a Division’s Tasks by Default
Scope Records Using Multiple String or ID Values in Record Criteria
Example Scenarios
These sample scoping rules provide relevant records to users.
Available in: Lightning Experience in Performance,Unlimited, and Developer editions. |
-
Display a Branch Location’s Records by Default
This scoping rule displays task records associated with a particular bank branch location by default. A custom field called Branch__c stores the bank’s branch locations. -
Display a Department’s Records by Default
This scoping rule displays contact records associated with a particular department by default for a user who works on them. The rule dynamically matches the contact owner's department with the current user's department. -
Display a Division’s Tasks by Default
This scoping rule displays records associated with a particular division by default for a user. -
Scope Records Using Multiple String or ID Values in Record Criteria
This scoping rule allows active users to scope the records they see to records whose Name__c field matches the rule’s record criteria value. The record criteria contains strings separated by a comma. ID values are also supported. Double-quotes specify that the value inside the quotes isn’t considered a delimiter.