Slack

Connect Slack to collect communications platforms evidence automatically.

Connect with OAuth

Before you start, an administrator of Slack must allow third-party apps:

• If your workspace requires approved apps, a Workspace Owner clicks Admin in the sidebar and selects Apps and workflows.
• Click Browse in the top right, search for and select the Safeguard app, and click Approve.
• (App approval itself is turned on under Admin › Apps and workflows › App management settings, Edit next to Require approved apps, Only allow pre-approved apps, Save.)

1. On Compliance › Connectors, open Slack, click Connect and choose OAuth.
2. Sign in to Slack and approve Safeguard on its consent screen. Use an account that can approve apps for your organization, usually an administrator. Safeguard asks for team:read, users:read.
3. You return to Safeguard, and the card shows Verified once the first check succeeds.

Connect with an API token

1. In Slack:

   1. Go to api.slack.com/apps, choose Create an app, select Blank app and click Continue. Enter an App Name, pick your Workspace and click Create.
   2. Open OAuth & Permissions. Under Scopes › Bot Token Scopes, click Add an OAuth Scope and add users:read and users:read.email.
   3. Click Install to Workspace and then Allow.
   4. Back on OAuth & Permissions, copy the bot token (it starts with xoxb-) from OAuth Tokens.

   Slack's public documentation does not cover every step.

   Bot tokens start with xoxb-. The fetched pages do not say whether the token can be viewed again, and do not name the bot token field beyond 'access token under OAuth Tokens'. Where the workspace (team) ID or URL is shown for the optional Account field was not sourced. App approval is available on all subscriptions.

   Source: docs.slack.dev, docs.slack.dev, slack.com, checked 2026-10-07.

   The permissions Safeguard needs: users:read, users:read.email.

2. On Compliance › Connectors, open Slack, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp.slack.com/mcp is filled in. Sign in to Slack when asked. It lets Griffin AI search Slack; the compliance evidence comes from the OAuth or API token connection.

Frameworks

Safeguard's automated tests read Slack and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Communications Platforms connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks