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

# Slack

> Connect Slack to RAD Security for workflow notifications and alerts.

# Slack Integration Setup

This guide walks you through connecting Slack to RAD Security using OAuth, enabling automated notifications from workflows directly to your Slack channels.

<Note>
  **Important:** Slack is currently designed for workflow notifications and is **not integrated with RADBot**.
</Note>

## Prerequisites

Before you begin, ensure you have:

<Check>Access to your Slack workspace</Check>
<Check>Access to RAD Security workspace with integration permissions</Check>

<Info>
  If your Slack workspace has app approval restrictions enabled, you may need to request approval from a workspace admin before installing the RAD Security app.
</Info>

***

## Configure in RAD Security

Setting up the Slack integration is simple and uses OAuth for secure authentication:

<Steps>
  <Step title="Navigate to Integrations">
    Go to your RAD Security workspace and navigate to **Data Sources** → **Integrations**.
  </Step>

  <Step title="Select Slack">
    Find and click on **Slack** from the list of available notification integrations.
  </Step>

  <Step title="Enter Integration Details">
    You'll be taken to a screen where you need to enter:

    * **Integration Name**: A descriptive name for this integration (e.g., `Slack - Security Team`)

    Click **Authorize** to begin the OAuth flow.
  </Step>

  <Step title="Authorize the RAD Security App">
    You'll be redirected to Slack's authorization page where you can:

    * Select the Slack workspace where you want to install the app
    * Review the permissions the RAD Security app is requesting
    * Click **Allow** to authorize the integration

    <Note>
      The RAD Security app will request permissions to post messages to channels and access basic workspace information.
    </Note>
  </Step>

  <Step title="Return to RAD Security">
    After authorization, you'll be automatically redirected back to RAD Security with the integration configured.
  </Step>
</Steps>

***

## Verify Integration

After completing the authorization flow, verify your integration is working:

<Steps>
  <Step title="Check Integration Status">
    Go to **Data Sources** → **Integrations** and locate your Slack integration.

    Verify that:

    * The status shows **Connected**
    * The workspace name is displayed correctly
  </Step>

  <Step title="Send a Test Notification">
    Configure a test workflow to send a notification to a Slack channel and verify the message is delivered successfully.
  </Step>
</Steps>

<Check>
  Your Slack integration is now configured! You can now receive workflow notifications and alerts in your Slack channels.
</Check>

***

## Configuring Notification Destinations

When setting up workflow notifications, you can specify where messages should be delivered in Slack:

### Send to a Channel

To send notifications to a specific Slack channel, provide the **channel name** in your workflow configuration:

* Use the channel name with or without the `#` prefix (e.g., `security-alerts` or `#security-alerts`)
* Works with both public and private channels

<Note>
  If you haven't added the RAD Security app to a private channel yet, you can invite it using `/invite @RAD Security` in the channel.
</Note>

### Send Direct Messages to Users

To send notifications directly to a specific user, provide their **email address** in your workflow configuration:

* Use the email address associated with the user's Slack account (e.g., `user@company.com`)
* The user will receive a direct message from the RAD Security app
* No additional setup required - the app can send DMs once authorized

<Info>
  **Tip:** Use direct messages for notifications that require immediate attention from specific individuals, such as security incidents assigned to on-call engineers.
</Info>

***

## What Notifications Are Sent

<AccordionGroup>
  <Accordion title="Workflow Completion" icon="circle-check">
    * Notifications when automated workflows complete successfully
    * Summary of workflow actions taken
    * Links to detailed results in RAD Security
  </Accordion>

  <Accordion title="Security Alerts" icon="triangle-exclamation">
    * Critical security events detected by workflows
    * Threshold violations and policy breaches
    * Urgent issues requiring immediate attention
  </Accordion>

  <Accordion title="Custom Workflow Events" icon="bell">
    * Custom notifications configured in your workflows
    * Scheduled report summaries
    * Integration status updates
  </Accordion>
</AccordionGroup>

***

## Use Cases

<CardGroup cols={2}>
  <Card title="Workflow Monitoring" icon="chart-line">
    Receive real-time updates when security workflows complete, keeping your team informed of automated actions.
  </Card>

  <Card title="Incident Response" icon="siren">
    Get immediate alerts in dedicated incident response channels when critical security events are detected.
  </Card>

  <Card title="Team Collaboration" icon="users">
    Share security findings and workflow results with relevant teams in their existing Slack channels.
  </Card>

  <Card title="Compliance Reporting" icon="clipboard-check">
    Automatically send compliance scan results and reports to stakeholder channels on a scheduled basis.
  </Card>
</CardGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authorization Failed" icon="triangle-exclamation">
    **Possible causes:**

    * Your workspace has app approval restrictions enabled
    * You don't have permission to install apps in the workspace
    * The OAuth flow was interrupted or cancelled

    **Solution:**

    * Check with your Slack workspace admin about app approval settings
    * Request approval for the RAD Security app if needed
    * Try the authorization flow again
  </Accordion>

  <Accordion title="Notifications Not Appearing" icon="bell-slash">
    **Possible causes:**

    * The RAD Security app hasn't been added to the target channel
    * Workflow notification settings are not configured correctly
    * The integration connection has expired

    **Solution:**

    * Invite the RAD Security app to the channel using `/invite @RAD Security`
    * Review your workflow notification configuration
    * Check the integration status in RAD Security and re-authorize if needed
  </Accordion>

  <Accordion title="Wrong Workspace Connected" icon="building-circle-xmark">
    **Possible causes:**

    * You were signed into a different workspace during OAuth flow

    **Solution:**

    * Remove the integration from RAD Security
    * Sign into the correct Slack workspace first
    * Create a new integration and complete the OAuth flow again
  </Accordion>
</AccordionGroup>

***

## Security Best Practices

<CardGroup cols={2}>
  <Card title="Channel Access Control" icon="lock">
    Only send sensitive security notifications to private channels with restricted membership to prevent information disclosure.
  </Card>

  <Card title="Regular Access Reviews" icon="user-check">
    Periodically review which Slack channels have access to RAD Security notifications and adjust as team members change.
  </Card>

  <Card title="Message Content" icon="message">
    Configure workflow notifications to avoid including sensitive data like credentials or PII in Slack messages.
  </Card>

  <Card title="Integration Monitoring" icon="shield-check">
    Regularly verify the integration status and re-authorize if needed to ensure continuous notification delivery.
  </Card>
</CardGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Notification Integrations" icon="bell" href="/rad-security/integrations/notifications/overview">
    Explore other notification integration options
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/rad-security/platform/workspace">
    Configure workflows to trigger Slack notifications
  </Card>
</CardGroup>