Encrypt Experience Cloud Site Data

You can add a measure of security to your Experience Cloud sites by encrypting files, attachments, and supported fields.

Note Beginning with Spring ’17, Shield Platform Encryption no longer masks encrypted data in the presentation layer. This change can affect some users’ ability to work with encrypted data. If you have data you don’t want specific users to see, revisit their field-level security settings, organization-wide sharing defaults, and object permissions.

Keep the following things in mind:

• You can encrypt data in Experience Cloud sites, but not in legacy portals.
• If you’re using Classic Encryption, data in encrypted custom fields is still masked.
• Your site’s specific settings for personally identifiable information (PII) apply regardless of whether data is encrypted.

• Data encryption doesn't change anything about the site user experience. However, encrypting the Account Name field affects how users' roles are displayed to admins. Normally, a site user’s role name is displayed as a combination of their account name and the name of their user profile. When you encrypt the Account Name field, the account ID is displayed instead of the account name.

  For example, when the Account Name field isn’t encrypted, a user belonging to the Acme account with the Customer User profile would have a role called Acme Customer User. When Account Name is encrypted, the role is displayed as something like 001D000000IRt53 Customer User.