> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incident-response/auto-create-incident-channel.md).

# Auto-Create Incident Channel

By default Pagerly runs an incident as a message and thread in your team (or a custom) channel. For higher-severity incidents you may want a **dedicated war-room channel** instead. Pagerly can create one automatically when an incident is declared.

## How it works

When enabled, on incident creation Pagerly:

1. Creates a dedicated Slack channel named after the incident (e.g. `inc-<title>-<id>`).
2. Sets the channel topic to the severity and title.
3. Invites the assignee and any responders.
4. Posts the incident message into that channel (so all updates, roles, reminders and comments live there).

## Configuration

Configure this per team under **Incident Settings → Channel & Update Reminders**:

* **Create a dedicated Slack channel per incident** — the on/off toggle.
* **Severities** — choose which severities get their own channel (e.g. only **SEV 1**). Leaving the list empty means *all* severities get a channel.

{% hint style="info" %}
Auto-creating channels requires the Slack app to have permission to create and invite to channels (`channels:manage`, `channels:write.invites`). If the toggle is off, no extra permissions are needed and incidents continue to thread in the team channel as before.
{% endhint %}

This keeps low-severity noise threaded while giving major incidents a focused space — without forcing channel sprawl on every alert.