1

I turned on Platform Encryption in a Dev Org. I have one user who can Manage Encryption Keys and View Encrypted Data and another who cannot.

Why can my user who cannot view encrypted data still view and edit data in encrypted fields (like Contact.FirstName and a field I added called Super_secret_secret__c).

2 Answers 2

1

I'm sorry @CharlesKoppelman, I hope it's better this way

Essentially view encrypted data is unrelated to shield encryption. Whether the user can read and/or edit the data from your custom object is subject to the regular rules (CRUD and FLS). If you want to prevent the user from reading and/or editing this field, please leverage FLS instead as you would do with other custom fields.

0

This is absolutely correct.

Manage Encryption Keys and View Encrypted Data permissions do not restrict users editing the encrypted fields. Users can edit the field values though they cannot view the data.

Refer Classic Encryption for Custom Fields

Encrypted fields are editable regardless of whether the user has the “View Encrypted Data” permission. Use validation rules, field-level security settings, or page layout settings to prevent users from editing encrypted fields.

6
  • Op says the user can still view the data
    – Eric
    Commented Mar 3, 2017 at 23:09
  • 1
    Just to elaborate a little bit, the view encrypted data used to be applicable to shield, hence maybe the confusion, but we are sun setting this behavior for shield, this user permission only applies to the classic encryption: releasenotes.docs.salesforce.com/en-us/winter17/release-notes/… The manage encryption keys do apply to Shield though, but this is a setup permission for controlling who can manage the keys themselves, such as creating or rotating keys Commented Mar 4, 2017 at 23:45
  • Yes, both users can view and edit all data. This does not answer my question. Commented Mar 5, 2017 at 9:34
  • @AlexandreHersans Can you explain why both users can view data in all fields and if I have control of that? Commented Mar 5, 2017 at 9:35
  • 1
    Essentially view encrypted data is unrelated to shield encryption. Whether the user can read and/or edit the data from your custom object is subject to the regular rules (CRUD and FLS). If you want to prevent the user from reading and/or editing this field, please leverage FLS instead as you would do with other custom fields. Commented Mar 6, 2017 at 0:21

You must log in to answer this question.

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