Skip to content

Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.

feat(deploy): route /messaging to switch-core, and say the tenant must exist

Petr Bauchc1763e3e2afe
diff --git a/deploy/remote/helm/switch/values.yaml b/deploy/remote/helm/switch/values.yaml
index 75fffe8dc..6aca7c16d 100644
--- a/deploy/remote/helm/switch/values.yaml
+++ b/deploy/remote/helm/switch/values.yaml
@@ -45,6 +45,7 @@ ingress:
- /mcp
- /oauth
- /.well-known
+ - /messaging
- /health
# Path prefixes served by the Teams bridge listener rather than the FastAPI
# app, because that listener is a separate HTTP server on its own port. Used
diff --git a/docs/old/bridges/SLACK_DISTRIBUTED_APP.md b/docs/old/bridges/SLACK_DISTRIBUTED_APP.md
index 3294bde14..04d6e0f1f 100644
--- a/docs/old/bridges/SLACK_DISTRIBUTED_APP.md
+++ b/docs/old/bridges/SLACK_DISTRIBUTED_APP.md
@@ -9,6 +9,11 @@ requires them to see a token at all.
They are two separate Slack apps and they will both exist. Nothing here
replaces the other page.
+The install connects a workspace to a tenant that **already exists**. Creating
+a tenant is Switch Console's job and is not reachable from Slack: the flow
+begins with an authenticated admin inside the tenant they are installing into,
+so no amount of clicking in Slack brings a tenant into being.
+
## Why it cannot be the same app
The self-registered app uses **Socket Mode**: Switch dials out to Slack and