vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-05 14:50:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify shared approval delivery

Browse Source
This commit is contained in:
Peter Steinberger
2026-03-30 08:02:58 +09:00
parent 52fb4a149a
commit d45b997ba9
3 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/channels/telegram.md
View File

@@ -812,6 +812,8 @@ openclaw message poll --channel telegram --target -1001234567890:topic:42 \
Approvers must be numeric Telegram user IDs. Telegram becomes an exec approval client when `enabled` is true and at least one approver can be resolved, either from `execApprovals.approvers` or from the account's numeric owner config (`allowFrom` and direct-message `defaultTo`). Approval requests otherwise fall back to other configured approval routes or the exec approval fallback policy.
Telegram also renders the shared approval buttons used by other chat channels. The native Telegram adapter mainly adds approver DM routing, channel/topic fanout, and typing hints before delivery.
Delivery rules:
- `target: "dm"` sends approval prompts only to resolved approver DMs