For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect StatusPal Next to Slack

Connect your Slack workspace so incidents reach your team where they already work: an announcement when one is declared, a channel per incident, and the right people pulled in automatically.

Connecting Slack is optional. What it changes is where the response happens: instead of asking people to watch a dashboard, the incident arrives in a channel with the commander and responders already invited.

This takes a couple of minutes. You need to be able to install apps in your Slack workspace.

What you get

  • An announcement when an incident is declared. StatusPal Next posts to a channel you choose, naming the severity and affected service, and linking to both the incident and its dedicated channel.

  • A channel per incident. Created automatically, with the commander and every responder invited. This one also needs a runbook with a Slack step. See Run your first incident drill.

  • Declaring and resolving without leaving Slack. The /spal commands, plus Post update and Resolve buttons on the pinned incident summary.

  • Your team matched to their Slack accounts, so channel invitations actually reach them.

Step 1: Authorize your workspace

Go to Settings → Slack Integration and click Add to Slack.

Slack Integration settings before connecting, showing the Connect to Slack card and the Add to Slack button

Slack asks which workspace to install into and shows the permissions being requested. Review them and confirm.

You are brought back to StatusPal Next, which confirms how many members it matched.

What StatusPal Next asks for, and why

Permission
What it is used for

channels:manage

Create the dedicated channel for each incident

channels:read

List the channels the app belongs to, so you can pick a notification channel

chat:write

Post the incident summary and the announcement

pins:write

Pin the summary to the top of the incident channel

bookmarks:write

Add the Manage Incident bookmark linking back to StatusPal Next

commands

Provide the /spal slash commands

users:read, users:read.email

Match your team members to Slack accounts by email

StatusPal Next never reads your existing messages. It cannot see a channel until the app is added to it.

Step 2: Add the app to a channel

This is the step people miss. Authorizing the workspace is not enough on its own: until the app has been added to at least one channel, there is nothing for it to post announcements into, and the page shows this.

Slack Integration settings showing the connected workspace, a warning that the Slack application is not installed in any channel, and the Synced Members list with one matched member and four unmatched

To fix it:

  1. In Slack, open the channel you want announcements in.

  2. Invite the app to it, for example by typing /invite @StatusPal Next in that channel.

  3. Come back to Settings → Slack Integration and refresh the page.

  4. Pick the channel from Notification Channel and click Update Channel.

Slack Integration settings after adding the app to a channel, showing the Notification Channel dropdown with a channel selected and the Update Channel button

Only public channels the app has been added to appear in that list. Incident channels StatusPal Next created itself are excluded, because the announcement exists to reach people who are not in the incident channel yet.

If the app already belonged to a channel when you authorized, StatusPal Next preselects one for you, preferring #general.

Step 3: Check your team is matched

Synced Members on the same page lists everyone in your organization with a green tick if they were matched to a Slack account, and an amber icon if they were not.

Matching is by email address, and it has to be exact. Someone who signed up to StatusPal Next with a personal address but uses their work address in Slack will not match, and will never be invited to an incident channel.

When you have fixed an address, click Re-sync Members. Syncing also runs automatically once a day.

Who can do what

Action
Who

View the Slack Integration page

Any member

Change the notification channel

Admins

Re-sync members

Admins

Remove the authorization

Admins

Disconnecting

Remove Authorization on the same page, which asks you to confirm. It clears the stored token, the workspace, the notification channel, and all member mappings, and StatusPal Next stops posting to Slack.

Channels that were already created stay in Slack, along with their history. Delete or archive them yourself if you want them gone.

Next step

With Slack connected, the fastest way to see it working end to end is a practice incident: Run your first incident drill.

Last updated