> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launchsafe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Connect Slack to LaunchSafe for real-time scan notifications and instant alerts when critical vulnerabilities are found in your applications.

The Slack integration sends real-time notifications to your team's Slack channel when scans complete, critical vulnerabilities are found, or scan failures occur.

## Setup

<Steps>
  <Step title="Navigate to Integrations">
    In the LaunchSafe dashboard, go to **Integrations** in the sidebar.
  </Step>

  <Step title="Connect Slack">
    Click **Connect Slack**. You'll be redirected to Slack's OAuth authorization page.
  </Step>

  <Step title="Select workspace and channel">
    Choose the Slack workspace and select the channel where notifications should be posted. We recommend creating a dedicated `#security-alerts` or `#launchsafe` channel.
  </Step>

  <Step title="Authorize">
    Click **Allow** to grant LaunchSafe permission to post messages to the selected channel.
  </Step>
</Steps>

## Notification events

LaunchSafe sends the following notifications:

### Scan started

Sent when a new scan begins. Includes the target name, scan type, and a link to the scan detail page.

### Scan completed

Sent when a scan finishes successfully. Includes:

* Severity distribution summary (e.g., "2 Critical, 5 High, 12 Medium")
* Total findings count
* Scan duration
* Direct link to results

### Critical finding discovered

Sent immediately when a critical-severity vulnerability is found — even before the scan completes. This ensures your team is alerted to the most dangerous issues as soon as they're confirmed.

### Scan failed

Sent when a scan encounters an error. Includes the error message and a link to the scan detail page for troubleshooting.

## Per-scan notifications

You can toggle Slack notifications for individual scans using the **Slack toggle** on the scan detail page. This is useful when:

* You're running a test scan and don't want to notify the team
* You're re-scanning after a fix and don't need duplicate alerts
* You want notifications for production scans but not development branch scans

## Webhook URL (alternative)

If you prefer more control over notification delivery, you can configure a **Slack Incoming Webhook URL** instead of the OAuth integration:

1. Go to **Settings** → **Notifications**
2. Enter your Slack webhook URL (starts with `https://hooks.slack.com/`)
3. Save

This approach lets you use Slack's workflow builder or route notifications to different channels based on your own logic.

## Message format

Notifications are formatted as Slack Block Kit messages with:

* Color-coded severity indicators (red for critical, orange for high, yellow for medium)
* Structured fields for scan metadata
* Action buttons linking directly to the scan or finding in LaunchSafe
* Compact, scannable layout designed to be read quickly in a busy channel

<Info>
  LaunchSafe only posts to the channel you selected during setup. It cannot read your messages, access other channels, or perform any other actions in your Slack workspace.
</Info>