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. records the new identity fields:SlackInstallation
Token resolution behaves the same over HTTP webhooks and Socket Mode. Events route by the installation identity in the envelope's field, which keeps routing correct for Slack Connect shared channels.authorizations
The adapter is also hardened for multi-workspace deployments:
Single-workspace installations are unaffected, and and work unchanged for both install types.getInstallationdeleteInstallation
Read the to get started.Slack adapter documentation
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 automatically, which Slack requires for workspace-scoped methods.
team_idRetried 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.