Skip to main content
Strix integrates with Slack to post vulnerability alerts and scan updates into a channel of your choice, mirror the discussion thread back into the Strix dashboard, and let your team update an issue’s status directly from Slack. This page covers setup, the bot scopes requested, what data is exchanged, and how to disconnect.

​
Overview

​
Setup

  1. In Strix, go to Settings → Integrations and click Connect on the Slack card. You must be an organization admin.
  2. Approve the app on Slack’s standard consent screen. Slack redirects back to https://app.strix.ai/api/integrations/slack/callback, where Strix stores the bot token for your workspace.
  3. Choose a default channel for notifications. For public channels the bot joins automatically; for private channels, invite @Strix to the channel first, then select it.
  4. Optionally adjust notification settings: which severities create alerts (critical, high, medium, low), and whether to notify on scan completion and on issue status changes.

​
Bot scopes requested

The bot only ever reads message threads that it started; it does not read general channel history, DMs, or files.

​
What data flows where

Strix → Slack:
  • New-finding alerts (for severities you’ve enabled): finding title, severity, target, and a link to the issue in Strix, posted to the default channel.
  • Optional scan-complete and issue status-change notifications.
Slack → Strix:
  • Replies in a Strix-created thread (message text, author name, avatar) are displayed alongside the issue in the Strix dashboard.
  • Status updates triggered from Slack (e.g. marking an issue in progress, resolved, or snoozed) update the linked vulnerability in Strix, recorded with the acting Slack user’s ID.

​
Security

  • Admin-gated: the install and callback endpoints require an authenticated Strix org admin, and notification settings can only be changed by admins.
  • CSRF-protected OAuth: the OAuth state is HMAC-signed, bound to the initiating organization and user, and expires after 10 minutes.
  • Token storage: the bot token is stored server-side in Strix’s database, scoped to your organization, and never exposed to the browser or other tenants.
  • Tenant isolation: inbound status updates from Slack are verified against the workspace’s team ID and only applied to issues owned by the organization linked to that workspace; thread reads are checked against the requesting user’s organization.
  • Private channels are opt-in: Strix never joins private channels itself — a workspace member must invite @Strix explicitly.
  • Audit trail: settings changes are recorded in the Strix audit log.

​
Disconnecting

An org admin can disconnect Slack at any time from Settings → Integrations, or via the API:
Required scope: integrations:write Disconnecting deletes the stored bot token and clears all Slack thread links from Strix issues. To fully remove the app from your workspace, a Slack workspace admin can also remove it under Slack → Manage apps.