Assess the impact of encrypting individual fields with Field-Level Encryption (FLE). If
a field is referenced by functions elsewhere in your Salesforce org, FLE can sometimes disrupt
those functions. The field analyzer flags any encryption schemes that are blocked by existing
configurations. Analyzing a field is required before you can encrypt it.
Required Editions
Available in both Salesforce Classic (not available in all orgs) and Lightning
Experience.
Available in: Enterprise, Performance, and Unlimited
Editions with the Salesforce Shield or Shield Platform Encryption licenses.
Available for free in Developer Edition.
User
Permissions Needed
To view setup:
View Setup and Configuration
To encrypt files:
Customize Application
Note This content relates to Shield
Platform Encryption. Read about implementing field-level encryption using Shield Extension
in Own from Salesforce.
Note At this time, you can view encryption blockers only. To view impacts besides blockers, such
as list views and report filters that can break due to encryption, use the analyzer in the
Shield Extension managed package.
To analyze one or more fields:
From the App Launcher, find and select Shield.
Go to the Platform Encryption tab, and then click
Field-Level Encryption.
Select the fields that you want to analyze.
Click Analyze Fields.
Close the confirmation window, or click Cancel Analysis if you want
to stop the request.
Salesforce runs the analysis in the background. You receive an email notification
when the process completes.
When you’re notified that the analysis is completed, return to the Field-Level Encryption
page and check the Result column for each field.
A checkmark icon indicates that no blockers were found. You can proceed
with turning on FLE.
A lock icon indicates that certain encryption schemes are blocked by other configurations
in your org. To use a blocked encryption scheme, first resolve the blocker by modifying the
associated configuration.
Review the specific blockers for each field as needed.
Click the dropdown menu for a field.
Click Review
Blockers.
In the Blocked Encryption Schemes column, see which schemes are
blocked.
To access a specific configuration that’s producing a conflict, use the link provided in
the Where to Fix column.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.