Connecting Slack to WatchDog Security#
Overview#
This guide explains how to connect Slack to WatchDog Security using OAuth authentication. Once connected, WatchDog will:Monitor your Slack workspace for security posture risks and configuration issues
Collect workspace and user inventory data
Deliver organization-level notifications and alerts to Slack channels via the Notification Center
What WatchDog Monitors#
WatchDog operates in read-only mode for monitoring and does not modify Slack configuration settings.
After the integration is connected, WatchDog may monitor:WatchDog uses the following Slack OAuth scopes:
| Scope | Purpose |
|---|
| channels:read | Read public channel metadata |
| groups:read | Read private channel metadata |
| mpim:read | Read group direct message metadata |
| im:read | Read direct message metadata |
| users:read | Read user profiles and status |
| users:read.email | Access user email addresses |
| users.profile:read | Read extended user profile data |
| team:read | Read workspace metadata |
| team.preferences:read | Read workspace configuration settings |
| files:read | Read file metadata |
| canvases:read | Read Slack canvas data |
| chat:write | Send messages to channels |
| chat:write.public | Send messages to public channels without joining |
| im:write | Send direct messages |
All monitoring-related permissions are read-only. Write permissions are used strictly for sending notifications via Notification Center.
Requirements#
Before connecting the integration, ensure the following:You have access to a Slack workspace
You're an Account Owner or Security Admin in WatchDog Security
The user connecting the integration has permission to install apps in the Slack workspace
The user has access to the channels where notifications will be delivered
Important Behavior#
Understanding how Slack monitoring and notifications work is important for correct setup.
WatchDog uses OAuth to access Slack workspace data in read-only mode
Notifications are sent via the WatchDog Slack bot
The bot must be added to a channel to send messages
Channel visibility is limited to channels accessible during authorization
If the bot is removed from a channel, notifications to that channel will fail
Step 1 — Open the Integration in WatchDog#
2.
Navigate to Management → Integrations
Step 2 — Authorize Slack#
After authorization is completed, you will automatically be redirected back to WatchDog Security.
You will be redirected to the Slack authorization page.1.
Select the Slack workspace
2.
Review the requested permissions
WatchDog will securely store the OAuth token and begin syncing workspace data.
Step 3 — Add WatchDog Bot to Channel#
Slack requires the WatchDog bot to be present in the selected channel2.
Navigate to the selected channel
3.
Run: /add apps to this channel
Once added, WatchDog can begin sending notifications.
Initial Sync#
WatchDog will begin collecting Slack workspace data
The initial synchronization typically completes within 5–10 minutes
Revoking Access#
To fully remove WatchDog access from Slack, revoke access in both WatchDog and Slack.Step 1 — Disconnect in WatchDog#
1.
Log into WatchDog Security
2.
Navigate to Management → Integrations
Step 2 — Remove Slack App#
1.
In Slack, navigate to: Settings & administration → Manage apps
This removes the bot and revokes access.
Troubleshooting#
Verify:
OAuth authorization completed successfully
The correct workspace was selected
Wait for the initial sync to complete