Slack is where a team notices things. Safeguard can post to it. The docs for Slack, Teams and Discord share one setup flow, and this guide covers the Slack parts.
What it is
Safeguard sends notifications into a Slack channel. The docs describe it as outbound: inbound commands are not available to enable today.
How to use it
Go to Settings → Integrations and click Connect on the Slack tile.
On the Credentials step enter a unique Integration Name, an optional Description and an Authentication Type.
- Bot Token (Full Access),
BOT_TOKEN: paste the token that starts withxoxb-, from OAuth & Permissions in your Slack app. - Incoming Webhook (Send Only),
INCOMING_WEBHOOK: paste the webhook URL that starts withhttps://hooks.slack.com/services/.
The Add to Slack button installs the Safeguard Slack app. Safeguard has no Slack OAuth callback, so you then copy the Bot User OAuth Token into the drawer by hand.
Click Next. Safeguard validates the credentials before it lists channels, and a failure shows an inline error. With a bot token you then pick a Default Channel from the fetched list. With a webhook there is nothing to pick, though you can type a display name.
If no channels appear, invite the bot to one with /invite @your-bot-name.
Limits worth knowing
Every integration sends everything to its single default channel. The data model has a channel mapping array, but no screen can create or edit mappings today. When you edit an integration, leaving credential fields blank keeps the stored credentials and skips re-validation.
The event catalog on the Webhooks and Events page lists what Safeguard emits, such as findings, scans, zero-days and policy violations. The chat page does not say which of them are posted to Slack, so test with a real event before you tell your team what to expect.
Quick check
Why do you paste the bot token by hand after clicking Add to Slack?
Because Safeguard has no Slack OAuth callback. Copy the Bot User OAuth Token into the drawer.
