Interface inventory: the text here is the text on screen.
Where it is: menu Data → Governance (address /governanca). The menu
shows this screen to the workspace owner.
Title Data governance, subtitle "Who sees what: access groups decide which tables, layers and personal data each person can see. Every block and every reveal of personal data is recorded in the audit log."
Right below, a strip with the current numbers: how many access groups, how many people with a policy, how many columns marked as personal data — and the Default: PII masked ("Without a group, the person sees everything with personal data masked.").
How personal data is found
On every pipeline load, the product checks the columns of all
tables (Bronze, Silver and Gold) by name — cpf, cnpj, email, telefone,
celular, rg, endereço, cep, nasc (catches dt_nasc and data_nasc), passaporte, and
nome when the table is about people — and by the value of a sample of rows:
CPF and CNPJ with a valid check digit (even in a column called documento),
email and phone. Whatever is found is flagged automatically and from then on comes out
masked. A column you unflag in Mark PII is not flagged again.
The flag applies by column name across the whole workspace.
The role decides what the person DOES; the group decides what they SEE
The role is set in Settings; the access group, here. A group change takes effect immediately in queries — the account owner is always unrestricted.
Create an access group#
1. Click New group
It's in the Access groups section.
2. Give it a name
In Group name (e.g., Analysts, Finance, Leadership).
3. Decide on personal data
Check Can see PII data in clear text (audited) only for those who need it. Without the check, the group sees personal data masked ("•••").
4. Choose the scope
In Allowed layers, click the layers the group can read. In Allowed tables (empty = all tables in the layers above), type the name and press Enter — or click one of the suggested tables. In Hidden columns, list what should disappear (e.g., margem, custo).
5. Click Create group
When editing an existing group, the button is Save group.
6. Put people in the group
In the People and what they see section, choose each person's group in the Group column. The change takes effect immediately.
With no groups, the screen suggests: "A good first pair: “Analysts”, Gold only and no PII; “Finance”, with PII in clear text."
Hide, mask, and deny are not the same thing#
The How restrictions work section explains the three:
| Effect | What the person on the other side sees |
|---|---|
| Hide | The item doesn't appear: the column leaves the result and the screen disappears from the menu. Whoever can't see it doesn't learn it exists. |
| Mask | The field appears, the value doesn't: personal data becomes "•••". |
| Deny | The action stays visible and the server refuses it with a reason. |
That's why Hidden columns and personal data are different things: a hidden column disappears from the dashboard, from Excel, and from email; personal data without permission appears as "•••".
The tables on the screen#
Access groups — columns Group · Personal data · Scope · People · Actions, with the PII in clear text or PII masked badge. Under Actions: edit, delete (Delete group — "Its members go back to the workspace's default policy."), and Connect BI, which creates a read credential with that group's access for external tools. Once created, the button becomes BI key, to download the key (the download is audited).
People and what they see — columns Person · Role · Data restrictions · Group. People without a group appear as No group · PII masked; people without restrictions, No data restrictions. The breakdown of what each role can do is in Settings → Access.
Marked personal data — the columns marked as personal data, in Bronze (table configuration) and in Silver (column grid). With none: "No column marked as personal data yet — mark them in the pipelines, at the Bronze step or in the Silver grid."
How far the policy applies today
The screen itself states: the policy applies to ingestia's screens, exports, and deliveries. Bringing it inside the datalake — also applying to anyone who queries the tables from outside — "isn't available on its own yet: to restrict direct access, contact support."
When the screen is empty#
- No group: "No groups yet. A good first pair: …"
- No people: "No members invited yet — invite them in Settings → Users."
Back to the app#
- Governance: Data → Governance
Next task#
- Governance and LGPD
- Connect BI screen
- Data console screen — where Reveal PII appears