Playbooks

A playbook is the ordered, battle-tested procedure for a recurring operation: a region failover, a key rotation, an incident response. When something is on fire, nobody should be improvising. The playbook is the calm, numbered path back to green.

Playbooks are available on the Pro and Enterprise plans. You need the Member role or higher to create one.

1. Create a playbook

1. Open Playbooks in the sidebar and choose + New Playbook.
2. Enter a Title, for example Region failover procedure.
3. Add any co-authors under Authors.
4. Fill in Body (Markdown). It starts from your workspace's playbook template, which by default has these sections:
   • Purpose: what the playbook is for, and the outcome it produces.
   • When to use: the trigger or scenario it addresses.
   • Prerequisites: access, tools, and knowledge needed before starting.
   • Steps: a numbered list, each step with what to do and the expected result.
   • Verification: how to confirm the procedure succeeded.
   • Rollback / recovery: how to undo the change or recover if something goes wrong.
   • References: related runbooks, dashboards, and points of contact.
5. Choose Create draft.

Code blocks in the body are syntax-highlighted, so commands can be copied straight from the page.

2. Get it approved

Playbooks use the shared review flow. Choose Propose for review and pick a reviewer, who can Publish, Reject, or Request changes. If changes are requested, work through the checklist and choose Resubmit for review.

Publishing means the procedure on screen is the one your team signed off. See Reviewing and approving for the full flow.

3. Keep procedures current

A published playbook can't be edited in place. When the procedure changes, write the updated playbook, take it through review, then open the old one and choose Supersede. If a procedure is retired entirely, choose Deprecate.

Tips

• Write each step as an action with an observable result, so the person running it knows when to move on.
• Put the stop conditions in Verification and Rollback / recovery rather than buried in the steps.
• Keep the When to use section specific. It is what people scan first under pressure.