Slack

Slack is the primary surface for the incident loop. Most teams acknowledge, investigate, and resolve without ever opening the dashboard.

Install

1. In the GreenSlope dashboard, go to Settings → Integrations → Slack.
2. Click Add to Slack and authorise.
3. Pick a default channel for alerts — typically #oncall or #incidents.

Alerts start landing in the default channel within a minute.

Routing rules

Routes pick the channel and escalation for an alert based on its tags. Configure them under Settings → Alerts → Routes. Rules are top-to-bottom; first match wins.

See Alerts for how severity and escalation combine.

Commands on alert messages

Every alert message in Slack has inline buttons:

• Ack — claim the incident. Stops escalation and stamps your name.
• Snooze — mute for a duration. Re-fires if still bad after.
• Drop — close with a reason (noise, dupe, intentional).
• Open in GreenSlope — deep-link to the alert detail view.
• Suggest rollback — if the Doctor page has a suspected-bad release, this button produces a Vercel rollback link for the right release.

Slash commands

/greenslope status           # open alerts, who's on them
/greenslope silence <dur>    # mute a fingerprint for a duration
/greenslope link <alert-id>  # drop the alert card into the current thread

/greenslope silence is the correct tool for knowingly-noisy periods (migration, load test). Silences are visible on the Doctor page as an amber banner — nothing is silently silenced.

Permissions

The GreenSlope Slack app requests the minimum scopes we can get away with. See the Security page for the full list and why each one is needed.

Uninstall

From Slack Settings → Manage apps, or from the dashboard. Remove from the workspace and we stop delivering.