> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adopt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting Doc Store access

> Grant which workstreams and agents can reach a Doc Store — the explicit access matrix behind what an agent is allowed to read.

Connecting files and creating an agent are separate from granting the agent permission to *read* those files. This step ties them together.

<Frame>
  <img src="https://mintcdn.com/adoptai-0ccbafe4/e2oYi85duHN1wflQ/images/acct-file-explorer.png?fit=max&auto=format&n=e2oYi85duHN1wflQ&q=85&s=521c7d8a910ffb76398c0d33d80dbb7e" alt="Doc Stores as they appear in the File Explorer for a workstream" width="1495" height="812" data-path="images/acct-file-explorer.png" />
</Frame>

## The two axes

Doc Store access is granted along the same two axes as everything else:

* **Which workstreams** can reach this Doc Store (usually just the client it belongs to).
* **Which agents** can read it (the agent that needs it, not every agent).

## Grant access

1. Open the Doc Store's access settings (the "Set Doc Store access" step in Advanced setup).
2. Confirm the **workstream** — normally the client that owns the files.
3. Grant the **agent(s)** that should read it (e.g. the R\&D agent gets read access; unrelated agents don't).
4. Save.

<Tip>
  **Least access.** Grant the narrowest access that lets the work happen — an agent should read only the Doc Stores it actually needs. This keeps the isolation guarantee meaningful and limits what any single agent can touch.
</Tip>

## Quick vs Advanced

On the Quick path this is handled for you — the template's agent gets read access to the client's files, nothing more. On Advanced, you set the matrix explicitly, which is what you want when a client has several agents that should see different things.

## Next steps

1. [Doc Stores and Data Stores](/core-concepts/doc-stores-and-data-stores)
2. [Access scoping](/security-access/access-scoping)
3. [Inviting members and setting access](/builder-guide/inviting-members-and-access)
