From 1b561652f16ebb59cbaa40a9b5bfd0ade4750f3e Mon Sep 17 00:00:00 2001
From: "@mrubens" <2600+mrubens@users.noreply.github.com>
Date: Thu, 5 Nov 2026 03:07:47 +0000
Subject: [PATCH] docs: clarify public-only Slack destination discovery

---
 apps/docs/fast-sessions.mdx                  | 6 +++++-
 apps/docs/providers/communications/slack.mdx | 9 ++++++---
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/apps/docs/fast-sessions.mdx b/apps/docs/fast-sessions.mdx
index 0c4d65cbfd..a8620a8638 100644
--- a/apps/docs/fast-sessions.mdx
+++ b/apps/docs/fast-sessions.mdx
@@ -380,7 +380,11 @@ channel-access checks. It does not infer access from the originating chat.
 
 Roomote uses one destination lookup and one send action for explicitly requested
 standalone messages. The lookup can return your linked Slack or Telegram account,
-linked people in shared Slack workspaces, and accessible Slack channels. Each
+linked people in shared Slack workspaces, and public Slack channels the Roomote
+app has joined. Private channels are not listed, so a missing channel does not
+mean Slack access was lost. Replies in the current conversation, including an
+automation's configured report channel, do not depend on finding that channel
+in the standalone destination lookup. Each
 lookup names one provider and destination kind. Self lookup resolves only your
 authenticated identity; people and channel lookup requires a targeted search or
 an exact destination reference. Results are bounded and include a continuation
diff --git a/apps/docs/providers/communications/slack.mdx b/apps/docs/providers/communications/slack.mdx
index 1ec7d8fee8..3aef3e4729 100644
--- a/apps/docs/providers/communications/slack.mdx
+++ b/apps/docs/providers/communications/slack.mdx
@@ -232,9 +232,12 @@ for example `@Roomote summarize this thread` or `@Roomote fix the failing CI
 job`. Replies in a Roomote-owned Slack thread continue that session; replies
 in an existing task-only thread continue the task.
 
-Roomote can read a bounded history from the current Slack channel, discover other
-channels in the same workspace, and post standalone updates to channels where
-the Roomote app is authorized. From another session surface, such as Telegram, you
+Roomote can read a bounded history from the current Slack channel, discover public
+channels the app has joined in the same workspace, and post standalone updates to
+authorized destinations. Private channels are not listed in the standalone
+destination lookup; their absence does not mean Slack access was lost. Replies
+in the current conversation, including an automation's configured report channel,
+do not depend on that lookup. From another session surface, such as Telegram, you
 can provide a Slack link or explicitly name Slack to read authorized context,
 then ask Roomote to send an update to an explicit workspace and destination.
 Roomote uses the same destination lookup and send action for your own linked Slack