# Chat SDK now supports Slack Enterprise Grid

DevFeed: [Chat SDK now supports Slack Enterprise Grid](<https://devfeed.tech/articles/chat-sdk-now-supports-slack-enterprise-grid-860.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/chat-sdk-slack-enterprise-grid>)

Author: Ben Sabic

Published: 2026-08-25T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Slack](<https://devfeed.tech/topics/slack.md>), [Bot](<https://devfeed.tech/topics/bot.md>), [API](<https://devfeed.tech/topics/api.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [bots](<https://devfeed.tech/tags/bots.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [events](<https://devfeed.tech/tags/events.md>), [http](<https://devfeed.tech/tags/http.md>), [identity](<https://devfeed.tech/tags/identity.md>), [routing](<https://devfeed.tech/tags/routing.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [slack](<https://devfeed.tech/tags/slack.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

## AI overview

Chat SDK's Slack adapter now supports Slack Enterprise Grid, allowing organization-wide bot installations to work across every workspace. The update adds enterprise-aware token resolution, tenant-scoped caches, event retry deduplication, workspace-aware API calls, and support for Grid user IDs in outgoing mentions.

## Source excerpt

Chat SDK's Slack adapter now supports Slack Enterprise Grid. Bots installed org-wide work across every workspace, with correct token resolution, tenant-scoped caches, and event retry deduplication. The adapter now stores org-wide installations by enterprise ID. This matches how tokens are resolved for incoming events, slash commands, and interactive payloads. SlackInstallation records the new identity fields: Token resolution behaves the same over HTTP webhooks and Socket Mode. Events route by the installation identity in the envelope's authorizations field, which keeps routing correct for Slack Connect shared channels. The adapter is also hardened for multi-workspace deployments: User profile and mention caches are scoped per installation, so one tenant's data never resolves for another. API calls made with an org-wide token pass the event's team_id automatically, which Slack requires for workspace-scoped methods. Retried event deliveries are deduplicated for 24 hours, covering Slack's Delayed Events redeliveries. Outgoing mentions accept W-prefixed Grid user IDs alongside U-prefixed IDs. Single-workspace installations are unaffected, and getInstallation and deleteInstallation work unchanged for both install types. Read the Slack adapter documentation to get started. Read more