Chat SDK Now Supports Slack Enterprise Grid

The Slack adapter for Chat SDK has officially begun supporting Slack Enterprise Grid. Bots installed across an organization now function correctly in all workspaces, with improvements to token resolution, tenant-scoped caching, and event retry deduplication.

The adapter now stores installations based on the Enterprise ID for org-wide installations. This aligns with the token resolution method for incoming events, slash commands, and interactive payloads. New identifier fields such as teamId, enterpriseId, and isEnterpriseInstall have been added to the SlackInstallation object.

Token resolution works identically for both HTTP webhooks and Socket Mode. Events are routed based on the installation identifier included in the authorizations field of the envelope, ensuring accurate routing even in Slack Connect shared channels.

Stability for multi-workspace deployments has also been strengthened.

• User profile and mention caches are scoped per installation to prevent data from one tenant from being exposed to another.
• When making API calls using org-wide tokens, the team_id required for workspace-scoped methods is automatically passed.
• Retried event deliveries are deduplicated for 24 hours to handle Slack's delayed event redeliveries.
• Outgoing mentions now accept W-prefixed Grid user IDs in addition to U-prefixed IDs.

Single-workspace installations are unaffected, and the getInstallation and deleteInstallation APIs continue to work as before for both installation types.