On this page
In short. An organization lists real names to hide (brands, products, competitors, people) and the roles that see an alias instead. The alias replaces the name on every reporting surface at once. Until an administrator chooses roles, editor and viewer see aliases while owner and admin see real names. The demo role always sees aliases.
How it works#
Terms are managed in Settings > Data masking ("Cài đặt > Che dữ liệu"); steps are in Set up identity masking. Each term carries:
- the real name as typed;
- an identity kind: brand, product, shop, creator, competitor, person, subsidiary, data source or campaign (only the kinds the organization's business areas use are offered; an organization running only Warehouse is offered none);
- a match rule: "In a sentence" (whole word), "Exact match" or "Starts with". There are no free patterns;
- an optional alias and an optional brand scope.
An organization keeps up to 200 active terms. The first rung that applies decides what a reader sees, in this order: an explicit override, the platform setting for the tenant, the organization's keyword list. The stored row keeps the real name, and an alias is never used as a lookup key.
Until an administrator chooses roles, editor and viewer see aliases while owner and admin see real names, so someone can always read the list back.
The demo role ignores the role list and the overrides: its holder always reads masked data on every surface above. Besides the organization's terms, the read adds (never stored, not counted toward the 200) the organization's real name mapped to its masked name (default "Tổ chức A" with a monogram) and each brand mapped to its curated replacement, else "Nhãn A", "Nhãn B"... in creation order. The masked name and logo are set in Settings > Data masking, card Organization identity when anonymised; a missing one falls back to the generic name or monogram, never the real value. A Demo member cannot create or edit share links. Content Intelligence data is not masked.
| Real name (stored) | Kind | Alias shown | Who sees the real name |
|---|---|---|---|
| "Acme Beverage Co." | Brand | "Brand A" | Owner, admin |
| "Nguyen Van A" | Person | "Person 3" | Owner, admin |
| "Rival Drinks JSC" | Competitor | "Competitor 2" | Owner, admin |
An AI suggestion button proposes terms from the organization's own data. It never sends values from a column flagged as personal data, and nothing is added until an administrator accepts the draft. Where masking applies is listed in Reference.
Where it stops#
- Masking is a display layer, not anonymization: the stored data keeps the real name, and no figure changes.
- The product's own chrome (brand switcher, menu pins) and the drill-down records behind a chart each follow their own switch.
- A super admin follows a configured scope only through an organization role they hold; holding Demo masks them in that organization.
- Rollout state: identity masking.
Reference#
Where masking is applied
| Surface | When it masks |
|---|---|
| Reports and dashboards | On the read path, for the person reading |
| Data assistant | The answer stream is filtered before it reaches the browser |
| Exports | The file carries what the screen showed |
| In-app inbox | At read time, for the person reading |
| External notification | The message is rebuilt per recipient |
| Alert generator | Keeps the real name; masking happens on read, never on write |
What it reads and never reads
| Reads | Never reads |
|---|---|
| The organization's terms, its role list and the reader's role | An alias as a lookup key |
| Brand terms for the pinned brand, plus organization-wide terms | Another brand's terms |