Tradeoffs and Limitations of Shield Platform Encryption
A security solution as powerful as Shield Platform Encryption doesn’t come without some
tradeoffs. When your data is encrypted, it’s possible that some of your users experience limited
functionality, and sometimes certain features aren’t available to them at all. As you design
your encryption strategy, consider the impact on your users and your overall business
solution.
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.
Note This content relates to Shield
Platform Encryption. Read about implementing field-level encryption using Shield Extension
in Own from Salesforce.
Field Limits with Shield Platform Encryption It’s good practice to use validation rules to enforce these field limits. In addition, because encrypted content is often longer than its ciphertext, encrypting a field can impose further limits on the values that you store in that field. Therefore, test your field limits in longer fields, such as Address and Subject, and on any encrypted field that contains non-ASCII values such as Chinese, Japanese, or Korean-encoded data.
Which Salesforce Apps Don’t Support Shield Platform Encryption? Some Salesforce features work as expected when you work with data that’s encrypted with Shield Platform Encryption. Others don’t. When FLE is used in addition to Database Encryption. Standard Shield Platform Encryption limitations apply.
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.