Slack App
Slack support is a first-class admin feature in the current application.
This page is a short reference summary of the Slack feature area. For the actual setup workflow, use the full guide:
This page is intentionally brief so it does not duplicate the task-based Slack setup guide.
What the admin UI exposes
The Slack admin page is one continuous surface grouped into:
- Connection
- Channels
- Behavior & Notifications
- Reminders
In the supported hosted flow, the connection card explains that the workspace uses the managed StatiBeat Slack app and shows the environment details relevant to that connection.
These sections are implemented in application/frontend/src/pages/admin/SlackSettings.jsx.
Configurable Slack settings
The Slack admin UI currently exposes the following settings family:
- shared announce channel ID
- global announce toggle
- global reminders toggle
- channel overrides toggle
- notify on create
- notify on update
- notify on resolve
- edit notification mode
- channel link mode
- behavior presets
- advanced per-event controls
- reminder interval minutes
- reminder interval lock
- workflow confirmation mode for AI-thread initiated actions
The Terraform provider models the shared channel, reminder, and core Slack app settings through statuspage_slack_app_settings and statuspage_slack_channel_reminder_settings.
The workflow confirmation mode currently lives in the admin UI only.
OAuth and setup behavior
The UI is built for OAuth-based Slack connection, and the backend exposes:
- public Slack link lookup by nonce
- admin Slack user link lookup
- admin Slack channel link status
- Slack app settings
- channel reminder settings
The application also includes a dedicated SlackLink route in the frontend for completing link flows.
Agent V5 workflows
The Slack admin page no longer stores provider credentials directly.
The backend Agent V5 runtime owns model configuration, grounding, permissions, action policy, and durable turn history. Slack settings only controls Slack connection behavior and how confirmations are posted when a workflow starts from a conversational thread.
Slash commands and explicit helper mentions remain the supported deterministic path. Natural-language app mentions and Slack assistant threads use the shared backend Agent V5 runtime after the linked Slack user and page permissions are checked.
Current conversational workflows cover incident lifecycle actions, maintenance lifecycle actions, Beat operations, Beat Group create/update, and grounded queries for incidents, maintenances, Beat state, audit history, analytics, and Slack linkage. Unsupported requests return explicit guidance plus a slash-command or helper alternative when one exists.
Grounded query answers come from backend capabilities rather than exact phrase matching. A request like Do we have any incidents ongoing? maps to active incidents, What historical incidents have we had? maps to resolved incident history, and Do we have any incidents in the past 24 hours? uses exact UTC time-window filtering before the response is drafted.
Beat Group awareness
Slack summaries and assistant-driven troubleshooting are now Beat Group aware.
- standalone Beats still read and alert as individual monitors
- grouped Beats keep their own evidence, but Slack can summarize the unhealthy Beat Group that owns incident and message behavior
- grouped investigation context points operators back toward the Beat Group-aware Beats workspace instead of assuming every failing signal is a standalone Beat