# Knowledge overview

Knowledge Base stores workspace documents that agents can reference. Documents are created once at workspace level, then selected in an agent configuration.

## Sources and status

An owner or admin can create text, upload supported files, import a public URL, and create folders. Workspace members can view knowledge, but mutation requires an admin-level dashboard session. Workspace API keys cannot mutate Knowledge Base.

A document is indexed when it is added. Its status is `indexing`, `ready`, or `failed`. Failed items remain visible for diagnosis. An agent can publish only when every referenced document exists and is ready.

Start with [add sources](/docs/knowledge/add-sources), then use [organize knowledge](/docs/knowledge/organize) when the library grows.

## How agents use knowledge

Attaching a document stores its ID in the agent configuration; it does not make a separate copy. Two retrieval modes are available:

- `auto` retrieves relevant chunks for each turn.
- `prompt` includes selected document content directly and performs no per-turn search.

Retrieved knowledge is treated as untrusted context, not as a replacement for system instructions. See [attach and retrieve](/docs/knowledge/attach-and-retrieve) for settings and verification.

## Ownership and deletion

Knowledge deletion is permanent. Deleting a document removes it from current branch tips and all drafts that reference it. Historical agent versions and conversation snapshots remain unchanged.

Bulk deletion with force is recursive for selected folders. A normal single-folder delete only succeeds when the folder is empty. Read [manage and delete](/docs/knowledge/manage-and-delete) before removing anything.