> ## Documentation Index > Fetch the complete documentation index at: https://docs.revyops.com/llms.txt > Use this file to discover all available pages before exploring further. # AI Documents > Instructions, guides, and shared notes your AI assistant uses in RevyOps. ## Overview AI Documents live in Settings under **AI Documents**. This page is only shown when your agency has workflows access. Each document is Markdown text that your AI agent can read, and in some cases write, when it works on your account. ## Document Types Every document has one of three types. The type is chosen when you create the document and cannot be changed afterward. | Type | Who can create it | What it's for | | ------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Agent Prompt** | Any agency | Instructions your agent follows at a single step in a workflow, such as researching an account or drafting a first email. Edit a prompt to change what your agent does at that step. | | **RevyOps Guide** | Only RevyOps | How RevyOps does things, written by RevyOps. Your agent reads these to know how to set up and run your account. | | **Shared Document** | Any agency | Your answers, decisions and notes. You and your agent both write here, so the document stays a record of how your account was set up and why. | RevyOps Guides are locked outside of RevyOps's own agency. A locked guide shows: > Locked. RevyOps keeps this up to date for you. Guides are locked because every client reads the same version, which is what lets RevyOps improve a guide and have the change reach you the same day. ## The Page The **AI Documents** page shows: * A **New folder** button and a **New document** button * A search box ("Search documents and folders") * A client filter ("Any client") * A table with columns Document, Type (with a "What are these types?" tooltip), Assigned to, and Last updated An empty folder shows "Empty folder. Add a document to it." ### Assigned To Each document has an assignment: | Value | Meaning | | -------------------- | -------------------------------------- | | **Not assigned** | Hidden, not visible to any client | | **All clients** | Visible to every client on the agency | | **Specific clients** | Visible only to the clients you choose | ### Deleting a Document Deleting a document warns you first: > Any AI agent step referencing this document will lose it. This cannot be undone. ## Shared RevyOps Guides RevyOps Guides are written and maintained by RevyOps in RevyOps's own agency, and are shared out to every agency automatically. They only appear for other agencies when assigned to all clients. Other agencies see these guides' folders as read-only in their own AI Documents list. ## Client Starter Copies When a new client is created, RevyOps can seed that client with a starting set of Shared Documents, copied from templates that live in a folder named **Templates / Client Starter** in RevyOps's own agency. Each client gets its own copy, assigned to that client only, placed in a folder named **Client Starter / \[client name]**. This seeding happens once per client, either when the client is created or the first time your AI agent reads AI Documents for that client. ## Folders: How Your Agent Finds Things Folders are how your AI agent finds its way around your documents. A full library is too large for an agent to read in one go, so it works the way a person would with a shared drive: 1. It lists the folders available to the client. 2. It opens the folder that matches what it needs, and lists the documents in it. 3. It reads one document at a time, or just the outline or one section of a long one. That means the way you organise folders decides what your agent reads, and what it skips. **What the agent sees** * Only folders that hold at least one document assigned to that client. A folder whose documents aren't assigned to the client doesn't appear for it at all. * Folder names, document names and document types. These are all it has to decide where to look, so name them for what's inside. * Nested folders, written with " / " between levels, such as **RevyOps Method / Templates / Client Starter**. **Folders RevyOps sets up for you** | Folder | What's in it | | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **RevyOps Method** | The RevyOps Guides: how to set up and run a client, split into chapters. Read-only. | | **Client Starter / \[client name]** | That client's own Shared Documents, such as the Worksheet and Signal Design. Your agent reads these, fills them in, and files new notes here. | **Tips for organising** * Keep one topic per document, so the agent can read exactly what it needs. * Use clear folder names that say what's inside, such as "Messaging" or "Objection Handling", not "Misc" or "New folder". * Put a client's working notes in that client's own folder, so they stay separate from shared material. * To move a whole library in at once, import a zip file. Each file's folder path in the zip becomes its folder. See [Agent Prompts and ICPs](/user-guide/agent-prompts-and-icps#zip-import). * Deleting a folder never deletes the documents in it. They move back to the top level. ## How Your AI Agent Reads Documents Your AI agent (through the MCP connection under Settings > Developer > MCP) can: * List the folders and documents available to a client * Read a document in full, by outline (headings only), or by a single section * Search documents by name and content * Create or update a Shared Document or Agent Prompt (an agent cannot create a RevyOps Guide) * Delete a document, but only one that is assigned to that client alone Your agent cannot edit or delete a RevyOps Guide, or a document shared with other clients. If it tries, it's told to create its own Shared Document in its own folder instead. Document content is capped at 64,000 characters. Agent Prompts used inside a workflow AI step are capped shorter, at 8,000 characters, at the point they're used in that step.