Slack Integration
💬 What the Slack integration does
Your admin connects a Slack app to Vamu once for the whole company. After that:
- Every user can get their own Vamu notifications as Slack direct messages with one click. Vamu finds their Slack account by their email, and each user picks which categories (risk, audit, compliance, …) go to Slack.
- Optionally, Vamu also posts a scheduled monitoring report to a channel your admin picks.
This guide has two parts:
- Part 1: Connect Slack (admins). Done once per company.
- Part 2: Get your notifications in Slack (every user). One click per user.
Part 1: Connect Slack (admins)
🔐 Prerequisites
- Permission to create and install apps in your Slack workspace.
- An admin role in Vamu, to connect the integration.
🔗 Step 1: Open Slack API Dashboard
Log in to Slack, then go to the
Slack API dashboard
🧱 Step 2: Create a New App
Click on Create New App
Choose the From Scratch option
Name the app Vamu, select your Workspace, then click Create App. Your users will see Vamu's messages coming from this app.
🔐 Step 3: Add the Bot Permissions
Navigate to the OAuth & Permissions section
Under Bot Token Scopes, add all of these. Vamu checks for them when you connect and tells you if any are missing.
| Scope | Why Vamu needs it |
|---|---|
chat:write | Send direct messages to users and post the report. |
chat:write.public | Post the report to any public channel without inviting the app first. |
channels:read | List public channels so you can pick the report channel. |
groups:read | List private channels the app has been invited to. |
users:read | Required by Slack alongside users:read.email. |
users:read.email | Find each user's Slack account from their Vamu email. |
If you add a scope after installing the app, click Reinstall to Workspace and copy the token again.
🚀 Step 4: Install the App and Copy the Token
Install the app in your workspace
You'll be redirected to allow the app. Click Allow
Copy the Bot User OAuth Token (it starts with xoxb-).
Optional: in App Home, turn on the Messages Tab. Users then see Vamu's direct messages under the app's own Messages tab in Slack.
✅ Step 5: Connect in Vamu
- In Vamu, go to Automation → Integrations, open the Slack notification integration and click Connect.
- Paste the OAuth Token from Step 4. That's all Vamu needs to connect your workspace.
- Optional, for the scheduled report: pick a Channel from the list, then a Frequency and Start date. Leave the channel empty if you don't want the report.
The channel list shows every public channel and any private channel the app has been invited to. To use a private channel, type /invite @Vamu in it first.
If you picked a channel, Vamu posts a "Slack Notification Connected" message there. You can add, change or remove the report channel later with Edit on the connected account.
Your users can now follow Part 2.
Part 2: Get your notifications in Slack (every user)
🔐 Prerequisites
- Your admin has completed Part 1. If they haven't, the Slack card in Vamu says so.
- Your Slack account uses the same email address as your Vamu account.
🔗 Step 1: Connect Slack
- In Vamu, click the notification bell, then Preferences.
- In the Slack connection card, click Connect Slack.
Vamu finds your Slack account using your email and sends you a direct message: "Vamu notifications are connected here." If it arrives, you're connected.
✅ Step 2: Choose Which Categories Go to Slack
In the preferences table, turn on the Slack switch for each category you want in Slack. The Frequency column applies to Slack as well: immediately, or bundled into a daily or weekly digest.
The Slack switches are greyed out until Step 1 is done. To stop, click Disconnect in the card. Your per-category choices are kept, so reconnecting brings them back.
Custom recipients only apply to email. They appear under the Email switch when email is on for a category, and they replace your own address for that category's emails.
Troubleshooting
| Message or symptom | What to do |
|---|---|
| "The Slack app is missing these permissions: …" when an admin connects. | Add the listed scopes from Part 1, Step 3, click Reinstall to Workspace, and paste the token again. |
| "Use the Bot User OAuth Token (it starts with xoxb-)." | You pasted a user token. Copy the Bot User OAuth Token instead. |
| "Invalid Slack token." or "This Slack token has been revoked." | Copy the token again from OAuth & Permissions. If it was revoked, reinstall the app first. |
| "This Slack workspace is already connected" | The workspace is already connected to Vamu. Edit the existing connection instead. |
| A private channel is missing from the channel list. | Type /invite @Vamu in the channel, then reopen the list. |
| "Your admin needs to connect the Slack Notification integration first." | Ask your Vamu admin to complete Part 1. |
| "No Slack account in the connected workspace uses …" | Your Slack email differs from your Vamu email, or you're not in that workspace. Ask your admin to check. |
| "The Slack app is missing the users:read.email permission." | Your admin needs to add the scopes from Part 1, Step 3 and reinstall the app. |
| The Slack switches are greyed out. | Finish Connect Slack. The card shows Connected when it's done. |
| Notifications stopped arriving. | Your admin may have disconnected the integration; the Slack card then asks for it again. Admins can also check Delivery logs, where each Slack attempt shows its status and error. |
✅ Done!
Your Slack integration is set up 🎉