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

# Knowledge

> Runbooks and notes that live on a team or service. Same editor, same folder model, scoped to the owner.

Every team and every service has a **Knowledge** tab. The UI is the same in both places; the difference is scope. A team's knowledge is shared across every service the team owns. A service's knowledge is specific to that service.

## Two streams: Runbooks and Knowledge

Inside the Knowledge tab you'll find two sub-tabs:

* **Runbooks** - step-by-step playbooks for handling specific failure modes. Warrn matches these to alerts during AI Triage.
* **Knowledge** - everything else: architecture notes, on-call onboarding, vendor contacts, design decisions.

Both are backed by the same editor and folder model. The split is mostly about findability and how Warrn uses them - runbooks are what the AI reaches for at alert time.

## Folder tree

Each sub-tab is a tree of folders. Folders can nest as deep as you want. Hover any folder for inline **+ document** / **+ folder** buttons, or use the **Create** button at the top right for a modal with the same options plus a description field.

Each document in the tree shows its title, reading time, author, and current status.

## Document status

Every document moves through three states:

| Status               | When to use it                                       |
| -------------------- | ---------------------------------------------------- |
| **Draft**            | You're still writing. Default for new documents.     |
| **Ready for Review** | Done writing, want a teammate to read it.            |
| **Published**        | Approved and stable. The version the team relies on. |

AI Triage prefers published runbooks. Drafts and review-state docs still exist, but they're treated as work-in-progress.

## The editor

Click any document to open the editor in an overlay. It's a Notion-style rich editor with auto-save - everything you type persists immediately, no save button.

* **Slash commands.** Type `/` for headings, lists, to-dos, tables, code blocks, images, blockquotes, and embeds.
* **Mentions.** Type `@` to mention a teammate.
* **Images.** Drag, drop, or paste them.
* **Live collaboration.** Multiple people can edit the same document together; cursors and selections are shown.
* **Versions.** Open the version panel to view or restore prior snapshots.
* **Table of contents.** Auto-generated from headings; click any entry to jump.
* **Writeagen AI assist.** Side panel that helps you draft, tighten, or restructure prose.

## Confluence-imported runbooks

If you've turned on Confluence runbook search ([service-level](/components/services/integrations#confluence-for-runbook-search) or [team-level](/components/teams/integrations#confluence-for-runbook-search)), pages the AI judges relevant get copied into Warrn as native runbooks. When you open one, the editor's status bar shows a Confluence badge linking back to the original page, so you always know where it came from.

You can also push a runbook **back** to Confluence using the export button in the same status bar.

## Where postmortems live

Postmortems are not in the Knowledge tab. They live on the [incident](/components/incidents) that produced them, with their own templates and workflow.