Slack (User Channel)
Employees open a DM with Dex in Slack — the same place work already happens.
The Slack User Channel lets every employee chat with Dex directly from Slack via direct message. It's the employee-facing conversation surface, installed into your workspace during onboarding. Unlike Microsoft Teams (which is covered by your M365 tenant consent), Slack requires its own app-level credentials — but those same credentials are shared with the Slack (Admin) integration, so you only enter them once. Today the channel supports one-on-one DMs only — @mentions inside shared channels and admin/CoAdmin workflows in Slack are on the roadmap.
What Dex does with Slack (User Channel)
This integration is employee-facing today — admin workflows are on the roadmap.
For employees (self-service)
- Send Dex a DM in Slack to open any IT request — "my VPN is down", "reset my password", "install Chrome"
- Receive proactive messages from Dex when your request completes or needs more info
- Approve or decline sensitive actions from Dex with one click in the Slack DM
- Keep the full conversation history in a single Slack thread — no separate portal to check
- Let Dex resolve identity automatically — your Slack email is matched to your directory record (Entra / Okta / Google)
Just ask Dex
Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.
Employee prompts
- >(DM to Dex) my laptop keeps freezing after the last Windows update
- >(DM to Dex) I need access to the Growth Analytics SharePoint site
- >(DM to Dex) reset my password — I'm locked out of Outlook
- >(DM to Dex) set up email forwarding to alex@acme.com while I'm on PTO next week
How to configure Slack (User Channel)
Onboarding takes minutes. Dex validates your credentials before saving them.
Setup steps
- 1In Slack, create a custom app for your workspace (or use the Dex-provided manifest) and install it — this yields a Bot User OAuth Token, Signing Secret, and App ID.
- 2In Dex, enable the Slack User Channel integration and paste the Bot Token, Signing Secret, and App ID.
- 3If you already enabled the Slack (Admin) integration, Dex reuses the same credentials — you only enter them once across both integrations.
- 4Employees immediately see Dex under "Apps" in Slack and can DM it. No per-user setup.
Credentials required
- botToken
- Bot User OAuth Token — starts with xoxb-, found at OAuth & Permissions after installing the app to your workspace
- signingSecret
- Signing Secret from Basic Information → App Credentials (used to verify inbound Slack events)
- appId
- App ID from Basic Information → App Credentials (starts with A)
Requirements
- •Slack workspace admin (or Primary/Workspace Owner) rights to install a custom app
- •Credentials are shared with the Slack (Admin) integration — enter them once, use across both
- •Conversation surface is DMs only today — @mentions in shared channels and CoAdmin usage are not yet supported
- •Dex uses the Slack user's email to match them to the company directory (Entra / Okta / Google) for identity resolution
- •For DMs to users, the bot needs im:write + users:read.email scopes (granted by the app manifest)
Related integrations
User ChannelsMicrosoft Teams (User Channel)
Employees open a DM with Dex in Microsoft Teams — right where they already work.
Learn more →- Collaboration
Slack
Run Slack admin operations and drive end-user conversations with Dex — all from one app.
Learn more → - Collaboration
Microsoft Teams
Manage Teams membership, route approvals to team owners, and send direct messages.
Learn more →
See Dex run Slack (User Channel)
Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.