# Atlas: permissions follow the data

> Knowledge, with permissions that follow the data.

Source: https://www.hexelstudio.com/atlas

**Knowledge for agents. Permissions follow the data.** Agents answer from what your company knows, and see only what the person they act for may see.

## Answers that know who's asking

Permissions come from the source, and are checked every time.

- **Both must be allowed.** When an agent acts for a person, it sees only what both of them may see.
- **From the source.** Permissions come with the data, groups expanded.
- **Always current.** Content is marked stale when its source or permissions change.
- **Live views into databases.** Queries you define, run as the caller under row-level security.

## The details

- **Offboarding:** When someone leaves, their access goes with them.
- **Fails closed:** Every retrieval path is checked. No check, no answer.
- **Sync your way:** On a schedule, by webhook or by change data capture.
- **Search:** Dense, hybrid and sparse, with reranking.
- **Knowledge graph:** Links what you know, and flags contradictions.
- **Disclosure receipts:** A record of what was shown, and to whom, ready for audit.

## Where Atlas sits

Orbit (for people) and your own agents (built with the SDK) sit on Titan: identity, policy, approvals, ledger, kill switch. Under Titan: Connections, Atlas, Memory, Router, Sandboxes, Harness, Routines, Skills, Waypoint. Everything runs on your ground (cloud, edge, on-prem, air-gapped), with Identity for sign-in.

## Runs where you run

From the public cloud to networks sealed from the world.

- **Cloud:** Live in minutes.
- **Edge:** Beside the work.
- **On-prem:** Your servers. Your walls.
- **Air-gapped:** Nothing gets out.

Built in: Fails closed; Disclosure receipts; Customer-managed keys; Runs air-gapped.

## Questions

### Where do the permissions come from?

From the source. Google Drive, SharePoint, Confluence, Jira, GitHub, Notion and Slack permissions are inherited, with groups expanded.

### What does an agent see when it acts for someone?

Only what both the agent and that person may see.

### What can Atlas connect to?

Those seven apps, plus S3, SQL, REST, Postgres change data capture, streaming and custom connectors. Agents reach it through about 26 MCP tools.

### Can it run in a sealed network?

Yes. Atlas ships as an air-gapped bundle, and works with customer-managed keys.

## Goes well with Atlas

- [Titan](https://www.hexelstudio.com/titan.md): Control for every agent.
- [Connections](https://www.hexelstudio.com/connections.md): Your apps and APIs. Agents never see a key.
- [Memory](https://www.hexelstudio.com/memory.md): Agents that remember between conversations.

---
Hexel Studio · https://www.hexelstudio.com · Index for agents: https://www.hexelstudio.com/llms.txt
