Below the AI
Permissions are enforced beneath the AI, not by it
The model writes the question. It never decides what you are allowed to see.
A minute in the product
Same app. View as a regional manager. Profit is refused in English.
Trust comes from governance, not the model
A regional manager asking about revenue gets their region -- not because the AI was asked nicely, but because the rest of the data never reaches it.
Every column declares itself
Restriction is a property of the data, not a rule someone remembered to write.
Check what others see
View the product as a scoped user and confirm the boundary holds before you rely on it.
Refusals explain themselves
A figure you may not see says so plainly, and says it is not an error.
What a refusal looks like
The tiles that are out of scope say so in plain language. They do not look like an error, and they do not invent a number to fill the hole.
Exports inherit the restriction
A CSV or PDF carries the same limits as the screen it came from. Retention controls what is stored; egress controls what is transmitted. They are separate settings, and we describe them as separate settings.