What stops one team from seeing another team’s data?
Separate workspaces per team, project or client, and every query passes both a workspace gate and a per-datasource permission gate before it runs.
Workspaces
A workspace per team, project, or client. Members belong to workspaces, and datasources are registered inside them, so the boundary is a structural one rather than a convention.
Two gates, both mandatory
Every query is checked against workspace access first, then against permission on the specific datasource. Failing either stops the query. Being a member of a workspace is not by itself permission to query everything registered in it.
What this is for in practice
Verticals with genuinely incompatible audiences sit side by side without bleeding into each other: a financial services estate, a revenue cycle estate, and a supply chain estate in one deployment, with no path between them. The same structure covers a services firm holding several clients, or a group holding company where the entities may not share data at all.
Where this comes from
See it against your own data
A pilot is scoped to one governed use case and time-boxed to eight to twelve weeks, with success criteria agreed before it starts.
Get started freeRelated questions
- What is dataface.ai?dataface.ai is on-source conversational analytics. Ask a question in plain English, and it generates read-only SQL from your schema metadata and runs it on the systems you already own. No warehouse copy, no pipeline.
- How do you run analytics without moving our data?dataface.ai reads your schema and a few example values per column, generates read-only SQL, and executes it on the source system itself. Your tables are never copied: no pipeline, no warehouse copy, no second place to secure.
- What does the LLM actually see from our data?By default the model sees your catalog: table names, column names, types, and a few example values per column. It never receives your tables, and it only sees query results if a user turns on AI analysis.
- How do you stop an AI from writing to or damaging our database?Generated SQL is SELECT-only. INSERT, UPDATE, DELETE and DDL are blocked, queries are parameterized against injection, and every request passes both a workspace gate and a datasource gate.