Everything in
one place.
Content from many systems, each with its own permission model, is combined into a single index with no permissions at all. The union becomes readable by anyone who can query it.
MKC2 results ↗An assistant indexed across every repository can answer questions no individual user was ever allowed to ask. Access control is what prevents that by construction.
01 / DEFINITION
The short answer first.AI access control is the enforcement of existing data permissions inside an AI system, so that a model answering a question can only use material the requesting person is entitled to see. It is applied at retrieval time, against the requester's identity, rather than to the finished answer.
The failure this prevents is specific and common. An assistant is built by indexing everything available, because indexing everything is the easy path and produces the most impressive demonstration. Once deployed, it answers questions using documents the asker could not have opened — and because the answer is synthesised prose rather than a file, no access log records a violation.
WORKED EXAMPLE
An analyst moves from the acquisition team to operations. Yesterday they could search draft acquisition plans; today they should see only operational material. The user interface reflects the new role, but the search index, a cached answer and the model session may still carry earlier results. An access-control test should inspect the complete path after the change takes effect.
Use an invented acquisition document and a test analyst. Verify the original authorised search, remove access and repeat through the search interface, conversational follow-up and export route. Check the data returned to the model, not only what appears on screen. Filtering an answer at display time is insufficient if an unauthorised passage has already entered a context available to other operations.
Keep a permitted operational document in the same index as a positive control. The analyst should continue to retrieve it after the transfer. If every search now fails, the system has demonstrated denial but not correct role-specific access. Inspect cache keys and session state to identify why different routes disagree.
Record the identity, resource, action, policy revision and result without copying the protected document into a general dashboard. This gives the access owner a precise regression test whenever group synchronisation, indexing or cache behaviour changes.
Further reading · NIST SP 800-207: Zero Trust Architecture
02 / WHY THE AI LAYER WIDENS ACCESS
Content from many systems, each with its own permission model, is combined into a single index with no permissions at all. The union becomes readable by anyone who can query it.
A generated paragraph drawn from a restricted document carries no trace of the restriction, so conventional access logging sees nothing unusual.
A pipeline authenticating with its own credentials makes every user as privileged as the pipeline. The most common single cause.
A fourth mechanism is cache sharing. A response cache keyed only on the question returns one user's answer to another, which defeats correct retrieval filtering entirely. Caches in AI systems must be keyed by identity as well as by query, or scoped per user.
03 / THE PATTERN THAT WORKS
The reliable arrangement is straightforward and has to be built in rather than added later. Every indexed unit carries the access metadata of its source. Every query is executed with the requesting user's identity attached, so the candidate set is restricted before relevance scoring. Caches are keyed by identity. Nothing enters the context window that the user could not have opened directly.
Two alternatives are worth naming because they are frequently proposed and both fail. Post-filtering — generating an answer and then checking permissions — is too late, because the restricted content has already shaped the response. Prompt-level instruction — telling the model not to use certain documents — is not a control, for the reasons set out in AI agent access control.
Permission freshness is the operational detail that catches teams out. Access changes constantly: someone leaves a matter, a confidentiality wall goes up, a document is reclassified. An index whose permission metadata is refreshed nightly is enforcing yesterday's permissions, which for a conflicts-of-interest boundary is not acceptable. Either query the authoritative source at retrieval time or keep the synchronisation lag inside what the strictest boundary tolerates.
04 / WHAT TO TEST
A standing test suite that queries for content each test identity should not reach, run continuously rather than once at launch.
Embeddings, caches, logs and evaluation sets each have their own access model. The boundary is only as strong as the weakest copy.
Permission metadata is the first thing lost when an indexing pipeline is rewritten, and nothing visibly breaks when it is.
Privilege AI treats this as part of the architecture rather than a configuration step: permissions and retrieval boundaries define which information a model can access and which actions it can propose. The retrieval-specific implementation is covered in RAG access control, and the derivative-copy problem in AI data security.
05 / QUESTIONS
Yes, if the index carries per-document access metadata and queries run with the requesting user's identity. What cannot be made to work is a permissionless index with filtering applied to the generated answer.
If any contributing passage is out of scope for the requester, it should never have entered the context. Filtering the candidate set before retrieval makes the combination question disappear rather than requiring a judgement about the answer.
As a hard filter at query time, sourced from the authoritative system and refreshed fast enough that a new wall takes effect immediately. A nightly synchronisation is not adequate for a boundary that exists to prevent a specific person seeing a specific matter.
Yes. An embedding is a derivative of the source text and informative about it, so it belongs under the same policy as the document. Storing vectors in an unrestricted index is a common and consequential gap.
This page is about which data an AI system may read on behalf of a person. Agent access control is about which operations an agent may perform. Most deployments need both, and they are enforced in different places.
WORK WITH PRIVILEGE AI
Keep your existing permissions meaningful.
We set up AI tools so people only see what they were already allowed to see, instead of the AI becoming a way around your access rules.
Decide access as part of the design.
We settle which information an AI system can reach and what it may suggest doing before it goes live, not after a problem.
Keep sensitive material in-house.
Where your data is confidential, we can run the system inside an environment you control.
Talk with Privilege AI
Tell us which roles, resources and actions your AI application must distinguish before returning information.
CONTACT PRIVILEGE AI
Tell us which roles, resources and actions your AI application must distinguish before returning information.
Privilege AI designs retrieval boundaries so that an AI layer inherits existing access control instead of bypassing it.