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

# Incident response playbooks overview

> Create and manage response playbooks that automatically attach to incidents based on conditions like severity, service, or team to guide resolution efforts.

## Overview

Playbooks are a great way to create a document that can help speed incident resolution. Think of them as a collection of simple instructions to empower someone to resolve a particular incident (even if they have minimal experience).

Playbooks are **automatically attached** to incidents when they **match a configured condition** (for example: severity, service, functionality, team impacted). If you have Playbooks or supported documentation hosted internally, you can link to them in the "External URL" field and provide detailed instructions in the content field.

In the above example, the **Database outage playbook** will be attached to any incident with the **SEV2 severity or the** **customers-postgresql-db** **microservices.** Please note that this is all OR logic currently, meaning this playbook will be attached to an incident that has just one of those matching conditions, such as SEV2 severity for example.

Additionally, at the bottom of the Playbook details page you have the ability to append any relevant tasking that needs to be done during the incident.

Playbooks are a great way to prevent a single person from becoming the de facto expert on how to resolve a particular problem. One person shouldn't be the only one who knows how to bring a critical system back online.

***

## Related Pages

<CardGroup cols={3}>
  <Card title="Example Usage with Incidents" icon="lightbulb" href="/configuration/example-usage-with-incidents">
    Walk-through of how playbooks auto-attach based on incident type and other properties.
  </Card>

  <Card title="Workflows Overview" icon="bolt" href="/workflows/workflows">
    The adjacent automation surface — event-driven actions that can complement playbooks during response.
  </Card>

  <Card title="Configuration Overview" icon="gear" href="/configuration/configuration">
    The umbrella page covering incident properties and configuration surface.
  </Card>
</CardGroup>


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