Document Slack agent reconnect and one-org install

[mintlify]

Summary

The upstream PR rearchitects the Slack agent install flow so that Slack consent runs first and the dashboard binds the workspace afterward. The change introduces two user-visible behaviors that previously weren't documented:

• Reinstall refreshes the token in place. When you reinstall the Slack app into a workspace that's already connected to your organization, Mintlify silently refreshes the stored bot token without requiring a re-bind, so existing channels, threads, and per-user integrations stay intact.
• One workspace, one organization. A Slack workspace can only be connected to a single Mintlify organization at a time. Attempting to install into a workspace that's already bound elsewhere now fails with a clear error.

Changes

• Added a "Reconnect or reinstall the agent" subsection to agent/slack.mdx describing how reinstalls behave.
• Added a Note callout under "Connect your Slack workspace" explaining the one-org constraint.
• Lightly tightened the existing install steps to reflect the consent-first ordering.

---

Note

Low Risk
Documentation-only updates describing Slack install/reinstall behavior; no runtime or security-sensitive code changes.

Overview
Updates the Slack agent setup docs to match the consent-first install flow (grant permissions in Slack, then confirm binding in the dashboard).

Adds a note that each Slack workspace can only be connected to one Mintlify organization, and documents a new Reconnect or reinstall section explaining that reinstalling refreshes the bot token in place without re-binding and keeps existing channel/thread/user integrations intact.

^{Reviewed by Cursor Bugbot for commit 4076e34. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify	🟢 Ready	View Preview	May 7, 2026, 7:27 PM