# Permissions that follow the data
2026-11-12. How Atlas keeps a source's permissions with its data, checks them before anything reaches an agent, and gives an agent only what both it and its user may see.
Source: https://www.hexelstudio.com/blog/permissions-that-follow-the-data
Published 2026-11-12 · By Hexel Studio
An agent working for you should see what you can see, and no more. Atlas makes that the default by carrying each source’s permissions with its data.
Give an agent a search index over your company’s documents and you have built a new way around your company’s permissions. The documents had owners and access lists in the systems they came from. The index doesn’t, unless someone puts them back. Then a question like “summarise the board pack” returns whatever ranked highest, including files the person asking was never meant to open.
Atlas is built so that doesn’t happen. Permissions come with the data, and every answer is checked against them.
## Copy the permissions, not just the content
When Atlas syncs a source, it records who may see each document along with the document itself. The connectors capture access lists from GitHub, Google Drive, Slack, SharePoint, Confluence, Jira and Notion. For Google Drive they also sync group memberships, so a file shared with a group is open to that group’s members and nobody else.
Atlas also links each person’s Hexel Studio account to the accounts they hold in those sources. A permission granted to a Slack user or a Google account then maps to the right person, whatever they are called in each system.
## Check before anything is disclosed
Search is where permissions usually leak, so Atlas checks there twice. Each indexed piece of a document carries a copy of its access list, and search filters on that copy first, so documents the person can’t open aren’t even candidates. Then every hit is checked again against the current access list before it is returned. The copy on the index only has to be close to current for good results; the second check is what keeps them safe. When a document’s permissions change, its indexed pieces are retagged as soon as the change is saved.
The same rule holds for the rest of what Atlas serves. Graph lookups are filtered by the document a fact came from, and a context bundle fails rather than return something it couldn’t check.
None of this depends on the agent behaving. Atlas applies the check on its own side, whatever the agent puts in its request. An agent can narrow a search, but nothing it sends can widen one.
## An agent sees the overlap
An agent acting for a person is two parties, not one. The person has their access. The agent has its own: what it was registered for, and what its task needs. Atlas uses the overlap. A document reaches the agent only if the person may open it and the agent may use it. An agent’s reach can be narrower than its user’s, never wider.
That is what makes a request like “summarise the Q3 board pack for Priya” safe to hand over. The agent builds the summary from the files Priya can open. Files she can’t are held back, and the record shows what was used.
## Leaving means leaving
Permissions change, and answers have to change with them. When someone leaves, removing their identity links takes away everything an agent could reach on their behalf, across every source at once. When a document’s access list changes in its source, the next sync carries the change into Atlas and onto the index.
Because every answer is checked against current permissions at the moment it is given, an old index entry can’t keep a revoked person’s access alive. Nor can anything derived from the documents: skills and memories built from a document carry its permissions with them.
## Why it belongs in the data layer
It is tempting to handle this in the agent: tell it which files to ignore, or filter its results in the application. Both depend on every agent and every application getting it right, every time, including the ones built next year by a team you haven’t hired yet.
Putting permissions in the layer that serves the data means there is one place they are enforced. Agents built by different teams, on different models, all inherit the same rule: you see what you could see. Never more.
---
Hexel Studio · https://www.hexelstudio.com · Index for agents: https://www.hexelstudio.com/llms.txt