From c522154771efa94c0524b856475f77e45ca04672 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=9D=92=E9=9B=B2?= <137844255@qq.com> Date: Thu, 5 Mar 2026 16:39:19 +0800 Subject: [PATCH] docs(telegram): recommend allowlist for single-user DM policy (#34841) * docs(telegram): recommend allowlist for single-user bots * docs(telegram): condense single-user allowlist note --------- Co-authored-by: echoVic --- docs/channels/telegram.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 8f0a70bf478..d3fdeff31ea 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -119,6 +119,8 @@ Token resolution order is account-aware. In practice, config values win over env If you upgraded and your config contains `@username` allowlist entries, run `openclaw doctor --fix` to resolve them (best-effort; requires a Telegram bot token). If you previously relied on pairing-store allowlist files, `openclaw doctor --fix` can recover entries into `channels.telegram.allowFrom` in allowlist flows (for example when `dmPolicy: "allowlist"` has no explicit IDs yet). + For one-owner bots, prefer `dmPolicy: "allowlist"` with explicit numeric `allowFrom` IDs to keep access policy durable in config (instead of depending on previous pairing approvals). + ### Finding your Telegram user ID Safer (no third-party bot):