Vercel Chat SDK adds Slack Enterprise Grid support for org-wide bot installs

What Vercel shipped

Vercel has added Slack Enterprise Grid support to the Slack adapter in its Chat SDK, according to a post on the Vercel blog. A bot installed once at the organisation level can now operate in every workspace of a Grid, and the adapter handles the details that previously made org-wide installs awkward: picking the correct token for each request, keeping cached data isolated between tenants, and ignoring Slack's redelivered events.

Org-wide installs and token resolution

The adapter now stores org-wide installations under the enterprise ID rather than a single workspace ID, and it resolves tokens the same way for incoming events, slash commands and interactive payloads. The SlackInstallation object returned from the OAuth callback carries new identity fields: for an org-wide install, teamId contains the enterprise ID (for example "E0123456789"), enterpriseId is set to that same value, and isEnterpriseInstall is true.

According to Vercel, token resolution behaves identically over HTTP webhooks and Socket Mode. Incoming events are routed using the installation identity found in the authorizations field of the event envelope, which the company says keeps routing correct even in Slack Connect shared channels, where a message can arrive from outside the installing workspace.

Hardening for multi-workspace deployments

Alongside Grid support, Vercel fixed several operational problems that surface once a bot spans many workspaces:

• User profile and mention caches are scoped to each installation, so cached data belonging to one tenant cannot be served for another.
• API calls made with an org-wide token automatically include the team_id taken from the event, a parameter Slack requires for workspace-scoped methods.
• Retried event deliveries are deduplicated for 24 hours, covering Slack's Delayed Events redelivery window, which stops a bot from acting twice on the same message.
• Outgoing mentions now accept W-prefixed Grid user IDs in addition to the usual U-prefixed ones.

Compatibility with existing installs

Single-workspace setups are untouched by the change. Vercel notes that getInstallation and deleteInstallation continue to work unchanged for both install types, so teams already running workspace-level bots should not need to modify their integration code. Vercel points readers to the Slack adapter documentation to get started.

Why it matters

Enterprise Grid is Slack's product for large, multi-workspace organisations, and org-wide installs have historically been a trap for bot developers: the familiar workspace-scoped assumptions around tokens, caches and event routing break down. By moving that Grid-specific complexity into the adapter, Vercel lets a Chat SDK bot serve an entire enterprise from one installation instead of forcing a separate install and token per workspace.

The finer details carry real weight here. Per-installation cache scoping is effectively a data-isolation guarantee between the tenants of a single bot, the kind of property enterprise buyers ask about before deploying anything company-wide. Deduplicating redelivered events for 24 hours removes a classic source of duplicated bot replies. And routing via the envelope's authorizations field, rather than a bare workspace ID, is what keeps behaviour correct in shared Slack Connect channels. For developers building Slack chatbots on Vercel's stack, this is a narrow but genuinely useful release.