Loading
Salesforce now sends email only from verified domains. Read More
Einstein Search
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Field-Level Security for Custom Fields in Search

          Field-Level Security for Custom Fields in Search

          Field-level security specifies whether users in your Salesforce org can view and edit each field in an object. You can configure field-level security settings separately from Einstein Search. Users can search a protected field only if they have the appropriate field permissions. However, search can only protect up to 100 searchable custom fields per object with field-level security, even if you set field-level security for more than 100 custom fields. The search engine matches results based on information in unprotected fields. You can select which custom fields are protected.

          Note
          Note All custom picklist fields are protected with field-level security and don’t count toward the 100 custom field limit.

          All standard fields, custom picklist fields, and the first 100 custom fields per object are protected. If an object has more than 100 custom fields, the extra fields are unprotected. Search Manager shows how many objects have unprotected fields. To ensure that all sensitive fields that can impact search results are protected or removed, review each object with unprotected fields.

          How Unprotected Fields Impact Search Results

          Even if you have unprotected fields in search, users can’t see the fields and records that they don’t have permission to access. However, if the user doesn’t have field permissions, the search engine still matches results based on sensitive information in unprotected fields. While users without permissions don’t see the field in their results, they do see results matched based on that field. Prevent unwanted results by protecting the field in search. 

          For example, if you add the Trade Union custom field to the Employee object and the Employee object already has 100 or more custom fields, apply protection in Search Manager. If you don’t protect this field, users can search for the trade union’s name and find all employees in that trade union. 

          Apply Field-Level Security to Custom Fields in Search

          Search can protect up to 100 custom fields per object with field-level security. For example, if you add the Trade Union custom field to the Employee object and don’t protect it, users can search for the trade union’s name and find all employees in that trade union. If an object has more than 100 custom fields, the search engine matches results based on information in the unprotected additional fields. 

          Required Editions

          Available in: Einstein Search in Lightning Experience
          User Permissions Needed
          To use Search Manager: Customize Application AND View Setup
          1. From Setup, in the Quick Find box, enter Search Manager, and then select Index Management.
          2. From the Salesforce Objects list, click the object that the fields are in. 
          3. Click Manage Field-Level Security for Search.
          4. Move up to 100 fields to the Protected list. If you have more than 100 fields to protect, move fields with less sensitive information to the Not Protected list. 
            If you can’t protect all fields with sensitive information, remove fields from the search index. See Manage the Search Index.
          5. Save your changes.

          Your changes are usually applied the next day, but it can take up to a few days. You can modify your changes after they’re applied.

           
          Loading
          Salesforce Help | Article