DocumentationGovernance Center
Dictionary
In the anymize dictionary you decide which terms are always anonymized and which never are, either only for you or for the whole team.
4 Min
What the dictionary is for
Detection is good, but it does not know your quirks. A project name like “Nordlicht” looks like an ordinary word and stays in clear text. Your own firm name looks like a client and becomes a placeholder every time, which makes every answer hard to read.
That is exactly what the dictionary is for. It corrects detection in both directions and does so permanently, in every chat and every document, instead of someone fixing it by hand each time.
Two lists, two directions
| List | What belongs on it | Effect |
|---|---|---|
| Always anonymize | Company names, projects, customers - everything detection misses. | The term is replaced by a placeholder in every document and every chat. |
| Never anonymize | Your product name, a specialist term, your own firm - everything wrongly treated as a name. | The term stays in clear text and reaches the AI model unchanged. |
You create an entry with at least two characters; capitalization does not matter. For “Always anonymize” you also pick the category so the placeholder carries the right type: Person, Organization, Place, Email, Phone, IBAN or Custom.
A term cannot sit on both lists. If it is already under “Always anonymize”, remove it there first before you put it on the exception list.
Personal or for the team
When creating an entry you decide with two buttons: “Only for me” or “For the team”. The difference is larger than it looks.
| Question | Personal entry | Team entry |
|---|---|---|
| Applies to | only you | all team members |
| Needs a team | no | yes |
| Who may create | every account for itself | Owners and Admins only |
| Typical case | a client only you work with | the firm name, an in-house specialist term |
The personal dictionary is deliberately available to every account, even without a team. It is not an admin feature but fine-tuning of your own anonymization, and that needs nobody else. Without a team only the team parts drop away on this page: the “For the team” button and the filter that switches between Team and Personal.
Only Owners and Admins may create team entries, because they change anonymization for everyone. That weighs especially heavy for “Never anonymize”: a team entry there leaves that term in clear text for every member.
Why is my own company name redacted?
Because detection cannot tell it apart from a client. From its point of view “Weber und Partner” is an organization, and organizations are protected. That it is you, it does not know.
So put your own name on the “Never anonymize” list as a team entry; then it applies to everyone immediately. From then on it stays in clear text again, and model answers read normally.
What happens when a team entry applies
Nothing anyone has to confirm. A team entry takes effect on the next operation: when anonymizing, the term is taken along or left standing. In the review view before send you see the result - one black box more or one less.
There is one exception. On the Compliance page you can set “Lock team dictionary” per group. For that group the shared dictionary is then neither read nor extended; they work only with their own entries. Anyone who still tries gets a message that access is locked for them.