Switch it on per base
Choose the bases concerned. The protection applies to new content added after it is switched on.
Data anonymisation replaces the identifying information it detects with neutral references, which only authorised users can restore.
Detection → Neutral references → Authorised access
Choose the bases concerned. The protection applies to new content added after it is switched on.
The information covered — names, email addresses or phone numbers detected — is replaced by neutral references.
The original values are kept encrypted. Restoring them remains subject to permissions.
Set up anonymisation for the chosen base before adding your content.
Add a document and review what was detected and replaced.
Check who can consult the content and restore the original values.
Keep the useful context of a document while replacing the identifying information detected. Check the result on your own formats before widening the use.
Not necessarily. If the identifiers can be restored, this is pseudonymisation. The distinction changes your obligations: settle it with your data protection lead.
Detection covers known formats. An identifier spelled out in the middle of a paragraph calls for a read-through: a check on a real sample is worth more than a promise.
The users you designate. Restoring is a right to be granted explicitly, base by base, not a global setting.
No. The protection is decided by how sensitive the corpus is: product documentation does not need it, a client file does. Switching it on everywhere slows processing without improving protection where it counts.