Document templates

Templates give every runbook, SOP, or postmortem the same bones. Creating a document starts from a template picker — pick a scaffold or a blank page — and the document arrives pre-filled with structure, tags, a title pattern, and the right document type.

The picker

Click New document (or Create from a space) and choose:

• Blank document — an empty page, always one click away.
• Any template — the body scaffold, tags, summary, and document type are pre-filled, and the title input starts from the template’s pattern (e.g. Runbook — ), ready for you to complete.

Six built-ins ship out of the box, each using the full rich-block vocabulary (callouts, Mermaid triage flows, severity tables, checklists):

Template	Type	What’s inside
Standard operating procedure	SOP	Purpose, scope, steps, verification checklist, escalation
Runbook	Technical	Symptoms, Mermaid triage flow, severity table, diagnosis, mitigation
Policy	Policy	Purpose, scope, numbered requirements, exceptions, enforcement
Meeting notes	Knowledge	Agenda, decisions, action items with owners
Incident postmortem	Technical	Blameless framing, impact table, timeline, root cause, follow-ups
Decision record	Knowledge	Context, options considered, decision, consequences

Placeholders

Templates use {{tag}} placeholders. Four fill in automatically the moment the document is created:

• {{title}} — the title you type (via the template’s title pattern)
• {{date}} — today’s date, in the workspace date format
• {{author}} — your display name
• {{space}} — the space’s name

Anything else — {{owner}}, {{attendees}}, whatever a template author invents — is left visible in the document as a prompt for the writer to fill in.

Per-space defaults

Each space can name a default template under Settings → Spaces → Edit → Default template. Creating a document from that space applies the template automatically — a bar above the editor shows which one, with Choose another and Start blank links so the default never traps anyone.

Managing templates

Admins manage everything under Settings → Templates:

• Edit any template — name, description, document type, tags, title pattern, and the body in the rich editor, with an insert-placeholder menu in the toolbar.
• Hide a template from the picker without losing its content.
• Reset a built-in to its shipped content at any time (built-ins can’t be deleted — hide them instead).
• Create custom templates from scratch — or open any existing document and use Save as template in its page actions to turn a real document your team likes into a reusable scaffold.

Every change is recorded in the audit log.

Templates over the Claude connector

The Claude connector is template-aware. A list_templates tool hands Claude each template’s full structure, and create_doc accepts a template parameter — so “draft a runbook for the payment gateway” lands in your team’s runbook shape: right type, right tags, right title pattern, right sections. Claude can follow the scaffold while writing its own content, or let the template body stand with placeholders filled.