Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.incident.io/llms.txt

Use this file to discover all available pages before exploring further.

A post-mortem that nobody reads is a post-mortem that nobody learns from. Once you’ve finished writing, you need to get it in front of the right people. There are two ways to do this: sharing via Slack to announce it, and exporting to get a copy into whatever tool your organization uses for long-term storage. You can also automate both of these with workflows.

​
Sharing via Slack

Sharing posts a message to one or more Slack channels with a link to the post-mortem. This is how you announce that a post-mortem is ready and get eyes on it. You can share from the post-mortem document or from the “Share post-mortem” task in the post-incident flow. When you share, you pick which channels to post to and review the message before it goes out.

​
Share templates

You can configure a default share template in Settings > Post-mortems that controls what the Slack message looks like. The template supports variables like the incident name, severity, and other incident properties, so the message is automatically populated with the right context. You can also configure default channels to share to, and choose whether to automatically include the incident’s own Slack channel.

​
Exporting

Exporting creates a copy of your post-mortem in an external tool. We support exporting to:
  • Google Docs
  • Notion
  • Confluence
  • SharePoint
Before you can export, you’ll need to connect the relevant integration for your external tool. You can do this from Settings > Integrations. Once the integration is connected, set up export destinations in Settings > Post-mortems. Each destination points to a specific location in your external tool (a Google Drive folder, a Notion database, a Confluence space, etc.), and you can have multiple destinations if you need to export to more than one place. When you export, the full post-mortem content is rendered into the destination, including the timeline and follow-ups. You can re-export after making edits to the document. Re-exporting does not overwrite your existing export, so there’s no risk of losing data. If an export fails (for example, due to a permissions issue or a deleted destination in your external tool), you’ll see an error message explaining what went wrong. You can fix the issue and retry the export. If you just want to grab the content without setting up an integration, you can use “Copy as Markdown” from the overflow menu in the editor.

​
External writing mode

If your team prefers to write post-mortems entirely in an external tool, you can set up a template with the “External” writing mode (see Templates). With this mode, the post-mortem is exported to your external tool immediately when it’s created, and you do all the writing there. See External documents for more on this workflow.