What is a Slack Connection? It's All About the Bot.

A Slack connection is built on top of the Slack OAuth flow and is specifically designed as a Bot connection. When a user creates a Slack connection, the OAuth process requests a set of scopes for a Bot Token. Once the user authorizes those permissions, Slack returns a Bot Token — this is the foundation of the Slack OAuth connection.

What Is a Slack Bot Token?

A Bot Token represents a bot associated with a Slack app installed in a workspace. Unlike User Tokens, a Bot Token is not tied to any individual user's identity — it is exclusively tied to the app itself. This makes bot tokens the recommended approach for most integrations.

How the Slack OAuth Flow Works

When a user creates a Slack connection, the following steps take place:

1. Connection Initiated — The user clicks to create a new Slack connection within the platform.

2. OAuth Scopes Requested — The platform requests the required OAuth scopes for the Bot Token from Slack.

3. User Authorization — The user is redirected to Slack, where they review and authorize the requested permissions for their workspace.

4. Bot Token Returned — Upon successful authorization, Slack returns a Bot Token; which is stored and used to authenticate API calls.

5. Connection Established — The Slack connection is now active and linked to the workspace.

One Bot Token Per Workspace Per App

Slack strictly enforces the policy of one Bot Token per Workspace per App. This is a fundamental constraint of the Slack platform and directly shapes how connections are managed. Installing the same app into the same workspace again does not generate a new token — it reuses the existing one.

Limitations:

In line with Slack's one-bot-token-per-workspace model, the following limitations apply:

• 1 connection to Workspace A → Allowed. One token per workspace is permitted.

• A 2nd connection to the same Workspace A → Not allowed. Slack only issues 1 bot token per workspace — duplicates are blocked.

• 1 connection to a different Workspace B → Allowed. A different workspace means a separate token.

• A 2nd connection to Workspace B → Not allowed. The same rule applies — maximum 1 connection per workspace.

Why This Limit Exists

This restriction reflects how Slack's authentication architecture works at a fundamental level:

• Single token identity — Slack issues one bot token per app per workspace. There is no mechanism to issue a second token for the same app-workspace combination.

• Duplicate prevention — Creating two connections to the same workspace would attempt to register the same bot token twice, causing conflicts and unpredictable behavior.

• Security and auditability — A single bot identity per workspace ensures that actions are traceable, permissions are clear, and there is no ambiguity about which connection is active.

Reference: https://docs.slack.dev/authentication/tokens#bot