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

# Manage documents

> Inspect, update, organize, and remove knowledge documents while checking current agent dependencies and stored content.

Treat each knowledge document as maintained source material. Give it a clear name, keep a record of who owns its content, and review affected agents before replacing or deleting it.

## Before you begin

You need access to the document's workspace and permission to manage knowledge. Keep the document ID and the original source. For initial creation, follow [Knowledge base](/agents-platform/configure/knowledge-base/overview).

<Steps>
  <Step title="Inspect the document">
    Read [document metadata](/api-reference/agents-platform/get-knowledge-base-document) and [stored content](/api-reference/agents-platform/get-knowledge-base-document-content). Check the type, intended source, and whether the stored representation includes the facts the agent needs.

    A folder organizes documents; it does not have document content of its own.
  </Step>

  <Step title="Review dependencies">
    Use [List agents using a document](/api-reference/agents-platform/list-agents-using-knowledge-base-document). Follow `next_cursor` while `has_more` is true. Keep the same filters when requesting another page.

    The list covers active agent references and related nonarchived branches. It is not a complete historical-version inventory. Review relevant saved versions separately before a destructive change.
  </Step>

  <Step title="Choose the matching change">
    Use the operation below for the source type. Review the proposed replacement before sending it; editing a shared document is different from changing an agent's attachment list.
  </Step>

  <Step title="Read the result back">
    Check the returned status, metadata, and stored content. Review indexes and any affected agent references separately. A successful update does not prove that a live conversation is using the new information.
  </Step>
</Steps>

## Choose an operation

| Task | Operation and review |
| - | - |
| Rename a document or update text content | [Update document](/api-reference/agents-platform/update-document); review the `name` and, for editable text content, `content` fields. |
| Replace a file source | [Replace file](/api-reference/agents-platform/replace-knowledge-base-file); inspect the replacement's stored content and processing state. |
| Refresh a URL source | [Refresh URL](/api-reference/agents-platform/refresh-knowledge-base-url); read the resulting content instead of assuming automatic synchronization. |
| Reorganize a source | [Move an item](/api-reference/conversational-ai/move-knowledge-base-item); confirm the destination folder and workspace. |
| Remove a source or folder | [Delete document or folder](/api-reference/agents-platform/delete-knowledge-base-document-or-folder); inspect dependencies and the intended scope first. |

Do not use a force-delete option merely to dismiss a dependency conflict. Decide how the referencing agents should change first. Bulk operations can report a different result for each item; inspect every result before treating the batch as complete.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does replacing a file prove retrieval is ready?" id="faq-manage-documents-retrieval">
    No. Inspect stored content and the relevant index state, then review [RAG](/agents-platform/configure/knowledge-base/rag). Source storage and live retrieval are separate checks.
  </Accordion>

  <Accordion title="Does a URL document stay synchronized automatically?" id="faq-manage-documents-sync">
    Do not assume that it does. Use the explicit refresh operation where supported and read back the content you intend to use.
  </Accordion>

  <Accordion title="Why is the dependency list empty for an old version?" id="faq-manage-documents-history">
    The dependency list is not a complete historical inventory. Inspect the version's saved knowledge locators directly before deleting a source it references.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.