Encrypt sensitive custom fields

Keep identifiers such as NRIC or passport numbers encrypted and masked, and reveal them only with a recorded reason.

For: Workspace admins (Enterprise add-on)

Steps

Open Settings → Custom fields and choose accounts, contacts, leads or deals.
For a new text field, tick Sensitive (encrypted and masked) when you add it. For an existing text field, select Mark sensitive in its row.
Existing values are encrypted in the background. The Sensitive column shows the progress; values are masked from the moment you mark the field.
On a record, people with the “Sensitive field values (reveal)” permission select Reveal, enter a reason and see the value for 60 seconds.
To find a record by a sensitive value, type the whole value in the list search.

Sensitive values are masked in lists, record pages, exports, the API, webhooks and automations, and are never sent to AI.
Search matches only the complete value (spaces, hyphens and letter case are ignored) — partial matches aren't possible by design.
Every reveal is recorded in the audit log with the reason. Marking a field sensitive can't be undone; delete the field if you no longer need it.

Still need help? Contact support

Keep identifiers such as NRIC or passport numbers encrypted and masked, and reveal them only with a recorded reason.

For: Workspace admins (Enterprise add-on)

Open Settings → Custom fields and choose accounts, contacts, leads or deals.
For a new text field, tick Sensitive (encrypted and masked) when you add it. For an existing text field, select Mark sensitive in its row.
Existing values are encrypted in the background. The Sensitive column shows the progress; values are masked from the moment you mark the field.
On a record, people with the “Sensitive field values (reveal)” permission select Reveal, enter a reason and see the value for 60 seconds.
To find a record by a sensitive value, type the whole value in the list search.

Sensitive values are masked in lists, record pages, exports, the API, webhooks and automations, and are never sent to AI.
Search matches only the complete value (spaces, hyphens and letter case are ignored) — partial matches aren't possible by design.
Every reveal is recorded in the audit log with the reason. Marking a field sensitive can't be undone; delete the field if you no longer need it.

Still need help? Contact support