Security & governance
Row-level permissions have a single enforcement point. Reports, AI, the API and the PG port all go through it.
05 · Governance
Same table, different people,
different rows.
Authentication, space authorization, row-level permissions and audit tighten in layers. Row permissions are enforced once, in the semantic layer, and reports, the AI assistant, the API and the PG port are treated alike. If no decision can be obtained, the request is refused, not allowed.
Try it: switch identity
Four entry points, one result
- Reports7,549,201.50
- AI assistant7,549,201.50
- API7,549,201.50
- PG port7,549,201.50
- 01
Identity
Accounts and OIDC sign-in. Before any data is touched, we check who you are.
- 02
Space and resource authorization
Assets belong to personal or team spaces, and folders and resources are granted to members.
- 03
Row-level permissions
A permission table decides which rows each person sees, enforced once in the semantic layer.
- 04
Audit
Key actions leave a record, so who did what and when can be looked up.
SQL in a sandbox
The SQL console runs in a restricted DuckDB sandbox with external file access turned off.
Outbound policy
Outbound requests from workflows and connections all follow one global outbound-access policy.
AI has your permissions
The assistant queries as the asker and does not inherit anything broader.
Take your datafrom tangled to clear.
Try it on sample data first, then bring your own.