Note: Still tidying up with test classes and documentation. Functionality seems to work reasonably well although I haven't done extensive testing
Salesforce provides Platform Encryption to encrypt sensitive fields at rest. Platform Encryption doesn's provide a standard mechanism to mask fields that are considered sensitive. Current available options for UX are as follows -
- Switch to classic encryption & use the masking feature. Be aware of differences between classic and platform encryption and considerations
- Provide access to unmasked sensitive fields through field level security or completely take away the access
- Create a custom solution
Typically information security compliance requires access to sensitive data to be provided only when required, to those who are authorized and log view/update activities.
This open source has been created as a reusable solution for the Salesforce community to provide quick starting point with all foundational capabilities such as -
- Configurable LWC record page component.
- Ability to specify dynamic fields specifications including masking through apex & permission to view & update. No standard Field Level Security access needs to be provided to these fields. Yet use Customm Permission to reveal and update access to specific fields.
- Optionally, provide custom apex Class.Method to log views & updates.
- Still working on adding comments to my code
- Still working on creating test classes to the apex classes