nonprofitCRM.org is produced by members of the NPSF (nonprofit salesforce.com) community. We are Salesforce.com administrators and consultants working to help nonprofits understand, better use and leverage Salesforce.com for their organizations. Read More
A colleague of mine (Lisa Glass) recently began using encrypted fields in Salesforce. It turns out they are fairly simple to use. Encrypted fields need to be requested through the “Feature Activations Team” at Salesforce. You can just open a Support Ticket and put in a request for this. As per the documentation, this feature is available to all Enterprise and Unlimited edition accounts, which means all NPO’s should be able to access this.
How it works:
Limitations:
Overall, this is a very powerful feature and you should consider leveraging it in your instance if your are storing any sensitive data such as Social Security Number, Credit Card Number, Medical Info, etc.
There is a lot more information on best practices and usage examples within Salesforce Help.
Encrypted fields are great. They have another limitation: If you do not have the “View Encrypted Data” permission, you cannot pass the full value when creating a child record via a custom button/URL. The button will pass the masked value only.
Be careful about credit card info, though. The official word from Salesforce is that encrypted fields aren’t “encrypted enough” to be fully compliant with industry standards. Encrypted field data isn’t encrypted on the database itself.
For PCI standards on credit card security, go here: https://www.pcisecuritystandards.org/tech/index.htm
Name (required)
Mail (will not be published) (required)
Website