Skip to main content
The Slack integration enables Living Security to send notifications directly to your Slack workspace. Notify users about training assignments, alert security teams about risk events, and keep managers informed about team progress.
For nudge and playbook delivery setup, start at Settings → Communications → Channels and click the Slack card. This page covers the underlying Slack app configuration.

Prerequisites

Before configuring the Slack integration, ensure you have:
  • Slack workspace admin or app installation permissions
  • Access to the Slack API portal at api.slack.com
  • Living Security admin privileges

Creating a Slack App

1

Create a new Slack app

  1. Go to api.slack.com/apps
  2. Click Create New App
  3. Select From scratch
  4. Enter an app name (e.g., “Living Security”)
  5. Select your workspace
  6. Click Create App
Your app appears in the Slack API dashboard.
2

Configure OAuth scopes

  1. In the left sidebar, click OAuth & Permissions
  2. Scroll to Bot Token Scopes
  3. Add the following scopes:
Only add the scopes your organization needs. Fewer scopes means better security.
3

Install the app to your workspace

  1. Scroll to the top of OAuth & Permissions
  2. Click Install to Workspace
  3. Review the permissions and click Allow
A Bot User OAuth Token appears starting with xoxb-.
4

Get your signing secret

  1. In the left sidebar, click Basic Information
  2. Scroll to App Credentials
  3. Copy the Signing Secret
Keep your signing secret private. Never share it in public repositories or logs.

Adding Credentials to Living Security

1

Navigate to Outbound Integrations

Go to Settings → Integrations → Outbound and click on the Slack card.
2

Add your credentials

Click Add Credential and enter:
string
required
Your Bot User OAuth Token starting with xoxb-. Found in OAuth & Permissions.
string
required
Your app’s Signing Secret. Found in Basic Information → App Credentials.
string
Optional. Required only for Socket Mode connections. Starts with xapp-.
string
Optional. A friendly name for this credential (e.g., “Production Slack”).
3

Save and verify

Click Save. The credential appears in your list with an active status.
Your Slack integration is now connected and ready to send notifications.

Notification Types

Once connected, Living Security can send the following notification types to Slack:

Troubleshooting

  • Verify the bot has been invited to the channel (/invite @YourBotName)
  • Check that chat:write.public scope is added for posting to public channels without joining
  • Confirm the channel ID is correct (use channel ID, not name)
  • Ensure you copied the complete token starting with xoxb-
  • Verify the app is still installed to your workspace
  • Check if the token was regenerated (requires updating in Living Security)
Slack limits API requests. If you see rate limit errors:
  • Reduce notification frequency
  • Consolidate multiple notifications into digest messages
  • Contact support for high-volume use cases

Best Practices

Create a dedicated Slack channel for Living Security notifications (e.g., #security-training) to keep alerts organized and reduce noise in general channels.
  • Use meaningful credential labels when managing multiple workspaces
  • Regularly audit which channels receive notifications
  • Set up notification digests instead of individual messages for high-volume alerts
  • Review Slack app permissions quarterly and remove unused scopes

Email Integration

Configure email as a delivery channel.

Teams Integration

Configure Microsoft Teams as a delivery channel.

Communication Log

Track Slack delivery status and history.

How to Set Up a New Integration

General integration setup guide.