You are here:
Criteria-Based Search and Filter Editions and Permissions
Review the supported products, editions, and required permissions for Criteria-Based Search and Filter.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Automotive Cloud |
| Available in: Enterprise, Unlimited, and Developer Editions with Consumer Goods |
| Available in: Enterprise and Unlimited Editions with Health Cloud |
| Available in: Enterprise, Unlimited, and Developer Editions with Manufacturing Cloud |
| Available in: Enterprise, Unlimited, and Developer Editions with Nonprofit Cloud |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Nonprofit Cloud for Grantmaking |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Public Sector Solutions |
Criteria-Based Search and Filter Permissions
Salesforce admins and users need the Use Criteria-Based Search and Filter system permission to configure and use criteria-based search and filter capabilities. The products and licenses in your org determine whether you have access to this permission and how you assign it. Typically, this permission is included in the Criteria-Based Search and Filter permission set.
Other Required Permissions
To let Salesforce admins and Analytics Cloud Integration Users transform and update data in the searchable object using Data Processing Engine (DPE), assign the Data Pipelines Base User permission set.
Users must also have the required object-level and field-level permissions for all source objects that are used in the search. Some products provide permission sets that include this object access. For example, in Automotive Cloud, the Automotive Foundation User permission set provides access to the objects and fields used in vehicle inventory search.
Customizing Permissions
If you customize this feature, such as adding fields, create a custom permission set. If you want to remove user permissions from the default permission set, create a muting permission set. Then, use permission set groups to assign users the default permission set in addition to your custom permission sets. This approach ensures users always have the latest default permissions and is an alternative to cloning permission sets.

