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

# Agent Access & RAG Indexing

> Let Bizzy agents search and retrieve content from your uploaded files

Files can optionally be made **agent-accessible**. When a file is
agent-accessible, Bizzy indexes its contents for retrieval — so an
[agent](/user-guide/agents/index) can pull relevant passages into its context
when answering questions.

## The agent-access flag

Every file has a boolean **agent access** flag:

| State                                      | What it means                                       |
| ------------------------------------------ | --------------------------------------------------- |
| **Agent Access** (default off for privacy) | The file's contents can be retrieved by agents      |
| **No Agent Access**                        | The file exists in Files but is invisible to agents |

The flag is set at upload time and shown as a badge on the file detail page.

<Frame>
  <img src="https://mintcdn.com/thebizzycomapny/LTbGbhRRJUQlFsAe/images/user-guide/files/agent-access-badge.png?fit=max&auto=format&n=LTbGbhRRJUQlFsAe&q=85&s=45fd80b270682a8ad469bbaab460062d" alt="Agent access badge on file detail page" width="800" height="500" data-path="images/user-guide/files/agent-access-badge.png" />
</Frame>

## How indexing works

When you enable agent access:

1. Bizzy splits the file into semantic chunks using a **structural markdown
   chunker** — sections, paragraphs, and other structural boundaries rather than
   fixed-size windows.
2. Each chunk is embedded and stored in the retrieval index.
3. When an agent needs information, it queries the index and receives the most
   relevant chunks back as context.

This approach (RAG — retrieval-augmented generation) keeps the agent grounded in
your actual documents rather than relying on its generic training.

<Note>
  There is no UI indicator for index status today. Once you enable agent
  access, give the system a minute to finish indexing before relying on the
  file's content in an agent chat.
</Note>

## Turning agent access on or off

Edit the file (via its detail page) and toggle **Agent access**. Turning it off
removes the file from the index; turning it back on re-indexes.

## What content agents see

Agents see the file's **text** — extracted from the document. Binary content
(images, raw PDFs without OCR) isn't indexed meaningfully; the indexer works
best with markdown, plain text, and documents with recoverable text layers.

## Privacy

Agent-accessible files are scoped to your organization. Agents in other
organizations never see them. Within your org, any agent that has the "read
files" tool permission can retrieve content.

## Next steps

<CardGroup cols={2}>
  <Card title="Uploading files" icon="upload" href="/user-guide/files/uploading">
    Enable agent access at upload time
  </Card>

  <Card title="Agents" icon="robot" href="/user-guide/agents/index">
    Configure which agent reads which files
  </Card>
</CardGroup>