Restriction Rules Developer Guide (Beta)
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
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)
Summer '21 (API version 52.0)
Restriction Rules
Considerations
Allow Users to See Only Specified Record Type
Allow Users to See Only Records That They Own
Allow Users to See Only Records Owned by Same Role
Allow Users to See Only Records Owned by Same Profile
Allow Users to See Records Based on a Custom Field
Newer Version Available
Example Scenarios
Refer to these sample restriction rules that fulfill different access
requirements.
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
-
Allow Users to See Only Specified Record Type
This restriction rule allows the designated users to see only contracts with a specified record type. -
Allow Users to See Only Records That They Own
This restriction rule allows users with the designated profile to see only tasks that they own. -
Allow Users to See Only Records Owned by Same Role
This restriction rule allows active users to only see events owned by users with the same role. You can use dot notation to traverse object and field relationships in the recordFilter field. -
Allow Users to See Only Records Owned by Same Profile
This restriction rule allows active users to only see events owned by users with the same profile. You can use dot notation to traverse object and field relationships in the recordFilter field. -
Allow Users to See Records Based on a Custom Field
This restriction rule allows high-volume users to only see contracts where the user's department matches the contract's department. This rule uses a custom field, Department__c, that must have the appropriate value set through Apex, Process Builder, workflows, or flows.