Incident channels
Every incident gets its own Slack channel, and once the incident is over that channel is a room nobody is reading. Firefight archives it after a delay you choose under Settings → Workspace. The messages stay in Slack and the incident keeps its timeline.
The setting is admin-only, like the rest of the Workspace page.
Choosing the delay
Section titled “Choosing the delay”Archive the channel offers a fixed set of delays, counted from the moment the incident ends:
| Choice | What happens |
|---|---|
| Immediately | Firefight archives the channel as soon as the incident is resolved or cancelled. |
| 15 minutes, 1 hour, 6 hours, 24 hours | The channel stays open for a short wrap-up, then archives on its own. 1 hour is the default. |
| 3 days, 7 days, 30 days | The channel stays open long enough to write the postmortem in it, then archives. |
| Never | Firefight leaves every incident channel open. Archive them yourself in Slack when you want to. |
Pick one and press Save changes. Choosing Never keeps the delay you had, so switching archiving back on later returns to it rather than to the default.
When it applies
Section titled “When it applies”The delay starts when an incident is resolved or cancelled, whichever ends it, and when an incident is marked as a duplicate of another, since the duplicate’s channel is over too.
A change to the setting applies to incidents that end after you save. An incident that was already resolved keeps the delay it was given when it ended.
Reopening an incident unarchives its channel, and Firefight skips the archive for an incident reopened before its delay runs out, so a team that has gone back to work in the channel keeps it.