After this article
You will be able to connect Slack to Lumos to sync users, roles, and user groups, enable Slack request/approval notifications, manage licenses, and suspend Slack user accounts, with the option to connect read-only for visibility and notifications only.Capabilities
Activity tracking is supported: Lumos syncs last-activity data (the last date a user posted a message or read a channel or DM). A blank value means the user had no Slack activity for at least 90 days before connecting, Slack only returns 90 days of history. Lumos caches earlier values. Lumos does not surface the Slackbot account, but other bots appear.
Required plan and roles
- Lumos plan: no minimum plan needed.
- Slack plan: any plan can be connected for sync and notifications. Suspending Slack user accounts via Lumos requires the Business+ plan or above (suspension uses Slack’s SCIM API, which is plan-gated). The
admin.*scopes require Enterprise Grid. - Slack role: the connecting user must be a Workspace Admin. On Enterprise Grid they also need Org Admin/Org Owner at the Organization level.
User Token scopes:
Read-only option: if you do not allow admin scopes, choose the Custom Scopes version when connecting and remove
admin and users.profile:write from the User scopes to disable provisioning/deprovisioning. If your workspace is not on an Enterprise plan, also remove admin.users:read and admin.teams:read. The remaining scopes still let Lumos read users and teams and send notifications. If you reconnect Slack with new scopes, you must revoke your previous OAuth token in Slack first, otherwise Slack won’t request the new scopes.
Instructions
Phase 1: Connect in Lumos- Find the Slack card in your Lumos integrations (Reconnect or add new).
- If your company is on the Enterprise Grid plan, check the “Is Enterprise Grid?” checkbox. Otherwise, leave it blank.
- Click Connect Slack.
- Choose the correct workspace in the Slack pop-up, then click Allow.
- Enterprise Grid only: approve the Lumos app for your org and add it to any workspaces where you want to use it, see Slack’s guidance for approving an app for your org and adding an app to workspaces. Complete the OAuth connection signed in as a Grid org admin.
API Endpoints Used
Troubleshooting
Slack is connected but returns no users. On Enterprise Grid, approve the Lumos app in Slack and add it to your workspaces (step 5 of the instructions). Also verify the users are active members (not guests or deactivated), the token hasusers:read and users:read.email, and users have completed Slack profile setup.
Downgrading scopes is not working. Slack’s APIs do not support downgrading scopes by reconnecting. For User Token scopes, ask the Lumos team to revoke your current token, then reconnect. For Bot Token scopes, in Slack admin open Installed Apps, click ”…” on the Lumos app row, choose Uninstall from your organization, then reconnect the integration in Lumos.
The integration broke after migrating to Enterprise Grid. Grid migration changes the workspace identity from a team_id to an enterprise_id, so the original connection no longer matches (slash commands and approvals fail with dispatch_failed, and reconnecting is blocked). Fully disconnect the Slack tile in Lumos, revoke the Lumos app’s OAuth token and uninstall it in Slack admin, then reconnect with “Is Enterprise Grid?” checked, signed in as a Grid org admin. The fresh install creates a new bot, rename it via Installed Apps → App Details → Configuration if needed. If reconnecting still errors or two Slack tiles appear, contact support for identifier cleanup.
dispatch_failed when using the Lumos Slack app (no Grid migration involved). Make sure the user’s Slack account is matched to the correct Lumos user. Matching issues cause this error. If that doesn’t resolve it, uninstall the Slack app and reconnect to rule out installation issues.
Multiple Slack workspaces connected, which one sends messages? Lumos picks the Slack tenant with the most active (not suspended) users, even if another tenant has more total users.
Requestors/approvers aren’t receiving notifications. Enable Notify users via Slack under Settings → Notifications → Channel Preferences (requires Admin entitlements). The setting is not retroactive. It only applies to new requests.
“Missing required scope” or “Insufficient permissions”. Verify all required OAuth scopes were granted and reinstall the Slack app with the correct permissions.
Rate limiting (429 Too Many Requests). Slack enforces tiered API rate limits: Tier 2 (~20 req/min for most endpoints), Tier 3 (~50 req/min), Tier 4 (~100 req/min for admin endpoints), and SCIM (~180 req/min). The connector handles rate limiting automatically with backoff. Large workspaces simply sync more slowly.
Fully uninstalling the Lumos Slack app. In Slack, open the Apps section, click Lumos, right-click to open App details → Configuration, scroll to the end and click Remove, then confirm. After removal the /appstore slash command no longer appears and App home page notifications stop. Reconnect via the Slack card to restore them.
Can I connect the same workspace to Production and Sandbox Lumos tenants? No. A Slack workspace should only be connected via the Slack (Messaging) app to one Lumos tenant. Connecting to multiple tenants causes issues with Slack actions.