This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.
Have a privacy field that requires certain permissions or password protected for information stored such as social security numbers.
- services industry where private information from the clients is collected.
Yah, I second this.
Perhaps privacy could be set at a field permissions level on existing fields, regardless of editable or calculated?
On a similar obfuscation note, I’d like to have AtoB() and BtoA() Base64 support in both formula fields and also within Automation Scripts (although there’s a workaround for this).