Slack

The Slack connector supports Identity & Access collection from a Slack workspace. An optional domain filter can limit collection to users whose email addresses belong to selected domains.

Required values

• Bot User OAuth Token for the Slack application

Required access

Grant these bot token scopes:

• users:read
• users:read.email

Install the application in the intended workspace and use the domain filter when guest or external identities should remain outside the connector's scope.

Before you start

Create the credentials listed above in the provider’s administration tools.

Configure in Superviso

1. Open Settings → Connectors and choose Add connector.
2. Select Slack from Provider.
3. Associate the intended asset, or use the new-asset option when appropriate. Enable only the supported synchronization options you need.
4. Enter Bot User OAuth Token and review the optional Domains filter.
5. Recheck the required privileges, scope, and filters, then choose Create connector. Resolve any validation errors shown by the form.
6. Open the saved connector, choose Sync connector when available, and confirm the synchronization scope.
7. Open Logs, wait for execution to finish, and inspect the result and any errors. Open the relevant Identities, Privileges, or Resources page for the enabled integration to verify collected records.

Expected outcome

The connector is saved for Slack with the intended integration and collection scope. Synchronization logs show progress, results, and imported records.

If setup or synchronization fails

Check the exact account or organization identifier, required form values, credential validity, granted access, and selected filters. Inspect the failed log’s details before retrying. If only some records are missing, check their scope and provider permissions. For synchronization status and source-managed fields, see Connectors and synchronization logs.

Back to Providers