docs: say one Slack app reaches one bot in one project

[leoisadev1]

Summary

The Slack section of the channels guide never said that one Slack connection answers as one bot in one project. A reader could expect to mention the app in different Slack channels and reach different bots or projects, which Akeru does not do. The section now states the limit, explains how to use several bots (one Slack app and one connection per bot), says a bot holds one Slack connection at a time, and adds the project to the final setup step.

Evidence

The claims are checked against the server and Settings code:

• Each connection attaches to one bot and one project (attachChannelConnection in apps/server/src/channels/ChannelConnections.ts), and every inbound message goes to that bot and project whatever Slack channel it came from (startChannel dispatch in ChannelConnectionLifecycle.ts).
• A bot has one binding per service, and runtimes are keyed by bot and service (runtimeKey(bot.id, provider)), so a bot cannot hold two Slack connections.
• Akeru rejects a Slack bot token that another bot already uses (channelSecretIdentity returns slack:<botToken>, checked in assertChannelIdentityAvailable).
• Settings refuses to assign a connection to a bot that already has one for that service ("Unassign the channel already connected to this bot first", BotChannelsSettings.tsx).

vp fmt --check docs/user/channels.md passes. Not tested in a running app; this is a docs-only change.

Merge Danger

Door: two-way. Docs only, with an empty changeset.

Blast radius: the Slack section of docs/user/channels.md.

Created with Claude Opus 5.5 in Claude Code.

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Oct 6, 2026 1:38am UTC

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Confidence Score: 4/5

[Low risk] Clarifies Slack app and bot connection constraints in docs.

The PR appears safe to merge, though the project-move wording should be clarified.

Findings

1.  Existing messages do not move ▶

Summary

The PR clarifies that a Slack connection routes to one bot and project, describes using separate apps for multiple bots, and updates the setup step to include project selection. The project-move wording should distinguish future routing from existing conversation history.

_{Reviews (1) · Last reviewed commit: "docs: say one Slack app reaches one bot ..."}

[greptile-apps]

Existing messages do not move When a Slack connection moves to another project, its existing conversation history stays in the old project. An inbound message that reaches the new project starts a separate thread there. “All of that app’s messages move with it” could lead readers to expect their history to move too. Clarify that the project change affects subsequent routing, not existing history. Confidence in this issue: 5/5.

Suggested change

	To send one bot's Slack work to a different project, move the connection to that project. All of that app's messages move with it.
	To send one bot's Slack work to a different project, move the connection to that project. Messages routed after the move use the new project; existing conversation history stays in the original project.