Slack
Inspect workspace membership and security settings while keeping optional notification access separate.
Connect the evidence app
Have a workspace administrator or owner install a dedicated Slack app. Use a user token, not a bot token, with:
users:readusers:read.emailadminteam:read
Enterprise retention evidence also needs admin.conversations:read. Slack's admin permission is broad; review it before granting access. Sparta does not use this connection to call SCIM write operations.
Enter the user token in Sparta and run the connection check.
Identify the MFA source
If your identity provider enforces Slack MFA through SSO, set the connection's MFA source to SSO. Sparta skips the Slack-local MFA assertion in that mode. Retain the identity-provider evidence rather than treating a skipped check as proof of MFA.
Optional notifications
Notifications use a separate bot credential in the SLACK_NOTIFY_BOT_TOKEN Worker secret. Its scopes are chat:write, im:write, users:read and users:read.email. Invite the bot only to intended channels.
There is no automatic credential refresh for the evidence connection. Rotate credentials deliberately and verify collection afterward.