Skip to main content
Strix connects to Slack to post vulnerability alerts and scan updates into a channel that you select. Strix also shows the Slack discussion thread in the Strix dashboard. Your team can update the status of an issue directly from Slack. This page describes the setup, the bot scopes that Strix requests, the data that Strix and Slack exchange, and the disconnect procedure.

​
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 the standard Slack consent screen. Slack redirects back to https://app.strix.ai/api/integrations/slack/callback. There, Strix stores the bot token for your workspace.
  3. Select a default channel for notifications. The bot joins public channels automatically. For a private channel, first invite @Strix to the channel, then select it.
  4. If necessary, change the notification settings: the severities that create alerts (critical, high, medium, low), and the notifications for scan completion and issue status changes.

​
Bot scopes requested

The bot reads only the message threads that it started. It does not read general channel history, direct messages, or files.

​
What data flows where

Strix → Slack:
  • New-finding alerts (for the severities that you enabled): the finding title, severity, target, and a link to the issue in Strix. Strix posts them to the default channel.
  • Optional scan-complete and issue status-change notifications.
Slack → Strix:
  • The Strix dashboard shows the replies in a Strix-created thread (message text, author name, avatar) adjacent to the issue.
  • Status updates from Slack (for example, when a user sets an issue to in progress, resolved, or snoozed) update the linked vulnerability in Strix. Strix records the ID of the Slack user who made the change.

​
Security

  • Admin-gated: The install and callback endpoints require an authenticated Strix org admin. Only admins can change the notification settings.
  • CSRF-protected OAuth: The OAuth state is HMAC-signed and bound to the initiating organization and user. It expires after 10 minutes.
  • Token storage: Strix keeps the bot token server-side in its database. The token applies only to your organization. The browser and other tenants cannot see it.
  • Tenant isolation: Strix compares each inbound status update from Slack with the team ID of the workspace. Strix applies the update only to the issues of the organization that is linked to that workspace. Strix also checks each thread read against the organization of the requesting user.
  • Private channels are opt-in: Strix does not join private channels itself. A workspace member must invite @Strix explicitly.
  • Audit trail: The Strix audit log records the changes to the settings.

​
Disconnecting

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