From f7068a1349af466e68ebf6b4ceaaa2ac21e9b05b Mon Sep 17 00:00:00 2001
From: "@zimeg" <zim@o526.net>
Date: Mon, 6 Apr 2026 00:58:05 -0700
Subject: [PATCH] docs(slack): move authorship scopes

---
 docs/channels/slack.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/channels/slack.md b/docs/channels/slack.md
index 983401eb520..bb763f50839 100644
--- a/docs/channels/slack.md
+++ b/docs/channels/slack.md
@@ -285,6 +285,12 @@ openclaw gateway
 </Tabs>
 
 <AccordionGroup>
+  <Accordion title="Optional authorship scopes (write operations)">
+    Add the `chat:write.customize` bot scope if you want outgoing messages to use the active agent identity (custom username and icon) instead of the default Slack app identity.
+
+    If you use an emoji icon, Slack expects `:emoji_name:` syntax.
+
+  </Accordion>
   <Accordion title="Optional user-token scopes (read operations)">
     If you configure `channels.slack.userToken`, typical read scopes are:
 
@@ -308,7 +314,6 @@ openclaw gateway
 - Config tokens override env fallback.
 - `SLACK_BOT_TOKEN` / `SLACK_APP_TOKEN` env fallback applies only to the default account.
 - `userToken` (`xoxp-...`) is config-only (no env fallback) and defaults to read-only behavior (`userTokenReadOnly: true`).
-- Optional: add `chat:write.customize` if you want outgoing messages to use the active agent identity (custom `username` and icon). `icon_emoji` uses `:emoji_name:` syntax.
 
 Status snapshot behavior: