chore(sync): mirror docs from openclaw/openclaw@8b665e0d70

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "3766bbb6745f76e457543e8f28bf19445a6811eb",
-  "syncedAt": "2026-04-30T13:45:07.631Z"
+  "sha": "8b665e0d7066dd524fa87d08592e259b465a005f",
+  "syncedAt": "2026-04-30T13:48:03.163Z"
 }

docs/channels/slack.md

@@ -582,6 +582,8 @@ Current Slack message actions include `send`, `upload-file`, `download-file`, `r
     - `toolsBySender` key format: `id:`, `e164:`, `username:`, `name:`, or `"*"` wildcard
       (legacy unprefixed keys still map to `id:` only)
 
+    `allowBots` is conservative for channels and private channels: bot-authored room messages are accepted only when the sending bot is explicitly listed in that room's `users` allowlist, or when at least one explicit Slack owner ID from `channels.slack.allowFrom` is currently a room member. Wildcards and display-name owner entries do not satisfy owner presence. Owner presence uses Slack `conversations.members`; make sure the app has the matching read scope for the room type (`channels:read` for public channels, `groups:read` for private channels). If the member lookup fails, OpenClaw drops the bot-authored room message.
+
   </Tab>
 </Tabs>