3

I have enabled Salesforce Shield in a developer org of mine, checked "Encrypted" in the custom field definition detail, and proceeded to update a record with a new value in the encrypted field.

I then attempted to login to Salesforce with another user, one that does not have "View Encrypted Data" permission enabled but can see see the field values that should be encrypted.

Can anyone explain why this may be?

I ran the Encryption Statistics and can see that 1 record has been encrypted (my test record), so it has definitely been encrypted. I've double checked that the second logged in users Profile doesn't have "View Encrypted Data" and there are no additional permission sets assigned to the account.

Improve this question

1 Answer 1

Reset to default
7

You're confusing Salesforce Shield/Platform Encryption with Classic Encryption (encrypted fields).

The latter require the View Encrypted Data permission to view in plaintext, but that's not how Platform Encryption works. It's designed to encrypt data at rest for orgs that need it for compliance reasons, but it exists at a lower level than the field-by-field permissions. With Shield Platform Encryption, you still need to use field-level security to protect fields from users who shouldn't see them.

For more, see Classic Encryption for Custom Fields relative to Strengthen Your Data's Security with Shield Platform Encryption.

Improve this answer
2
  • Let's say if we have FLS for the field as read, so they still be able to see the data, it won't show them as encrypted right?
    – Anonymous
    Commented Oct 12, 2022 at 6:10
  • Yes, that is correct.
    – David Reed
    Commented Oct 12, 2022 at 17:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .