Skip to content

docs(slack): add missing Messages Tab setup step#3558

Closed
dashed wants to merge 1 commit into
NousResearch:mainfrom
dashed:docs/slack-messages-tab-setup
Closed

docs(slack): add missing Messages Tab setup step#3558
dashed wants to merge 1 commit into
NousResearch:mainfrom
dashed:docs/slack-messages-tab-setup

Conversation

@dashed

@dashed dashed commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add Step 5: Enable the Messages Tab to the Slack setup guide
  • Without this step, users see "Sending messages to this app has been turned off" when trying to DM the bot — even with all correct scopes and event subscriptions
  • Add troubleshooting entry for this specific error message
  • Renumber subsequent steps (5→6, 6→7, 7→8, 8→9)

Context

The Messages Tab in Slack's App Home settings must be enabled for users to send direct messages to the bot. This is a Slack platform requirement that isn't covered in the current setup guide. The existing docs cover scopes, events, and socket mode, but miss this critical App Home configuration.

Changes

website/docs/user-guide/messaging/slack.md:

  • New Step 5 with instructions + danger admonition
  • Troubleshooting table: new row for "Sending messages to this app has been turned off"
  • Steps renumbered to accommodate the new step

How to test

  1. Follow the Slack setup guide without enabling the Messages Tab
  2. Try to DM the bot → see "Sending messages to this app has been turned off"
  3. Enable the Messages Tab per the new Step 5
  4. DM the bot → messages go through

Platform

Tested on Slack workspace with Hermes Agent deployed via K8s (Socket Mode). The Messages Tab setting is a Slack API console configuration, platform-independent.

Without enabling the Messages Tab in App Home settings, users see
"Sending messages to this app has been turned off" when trying to DM
the bot — even with all correct scopes and event subscriptions.

Add Step 5 (Enable the Messages Tab) between Event Subscriptions and
Install App, with a danger admonition. Also add troubleshooting entry
for this specific error message. Renumber subsequent steps (6→7→8→9).
@dashed dashed marked this pull request as ready for review March 28, 2026 18:54
@teknium1

Copy link
Copy Markdown
Contributor

Merged via #3590 — your commit was cherry-picked onto current main with authorship preserved. Thanks for catching this missing step!

@teknium1 teknium1 closed this Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants