A space for each user
Every user gets a schema of their own. Their views open in Power BI, Excel or any SQL client by name.
The Sandbox
Analysts write their own queries anyway. The Sandbox gives each user a personal space for them: on the governed data, reachable from Power BI by name, and kept apart from the curated Mart.
In short
When a calculation lives in one person's Power BI file, nobody else can find it, check it or reuse it. In the Sandbox it is stored in the platform and served to every tool.
Every user gets a schema of their own. Their views open in Power BI, Excel or any SQL client by name.
A Sandbox view runs when it is queried, so it always reads the current data. Nothing is copied.
Whoever queries a Sandbox view gets only the values they may read.
Each change to a view is saved as a new version, with who made it and when.
How it works
Sandbox views read the Vault and the Mart. The Mart never reads a Sandbox view, so personal logic cannot slip into the curated layer.
The Mart never reads a Sandbox view
margin_checktop_customerschurn_watchregion_mixdraft · waits for benbudget_vs_actualPower BI · Excel · any SQL client
When a view proves useful to everyone, the team rebuilds it in the Mart, where changes go through a Mart Plan before they are published.
Proposals
A colleague can suggest a change to someone else's Sandbox view as a draft. The live view keeps running, and nothing changes until its owner approves.
A proposed change is saved next to the live view. Reports keep reading the live one.
The owner sees the draft next to the live view, then approves or discards it.
A coding agent can draft changes to its user's own views. It can never approve one.
A short live demo: an analyst writes a view, a colleague proposes a change, and the owner approves it.