Skip to content

[Docs] Clarify Slack destination discovery and current-conversation replies #3669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
roomote-community wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

[Docs] Clarify Slack destination discovery and current-conversation replies #3669

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion apps/docs/fast-sessions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
9 changes: 6 additions & 3 deletions apps/docs/providers/communications/slack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading