let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wip [skip ci]

Browse Source
This commit is contained in:
Onur
2026-01-08 14:03:06 +03:00
committed by Peter Steinberger
parent 678d704341
commit 96b4d885ac
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
tmp/2026-01-08-msteams-permissions-and-capabilities.md
View File

@@ -33,6 +33,7 @@ Works:
Does NOT work:
- **Image/file content** from channel or group chat messages (payload only includes HTML stub).
- Downloading attachments stored in SharePoint/OneDrive (requires Graph).
- Reading **message history** beyond the live webhook event (requires Graph).
- Accessing messages outside the installed team.
### With **Teams RSC + Microsoft Graph Application permissions**
@@ -40,6 +41,7 @@ Adds:
- Downloading **hosted contents** (images pasted into messages).
- Downloading **file attachments** stored in SharePoint/OneDrive.
- Full message/attachment lookup via Graph endpoints.
- Reading **channel/chat message history** via Graph.
Still **not** added automatically:
- 1:1 chat file support (requires separate Bot file flows if we want to support it).
@@ -79,6 +81,9 @@ Teams stores images and files in Microsoft 365 storage (SharePoint/OneDrive). Th
If Graph tokens are unavailable (permissions missing or no admin consent), image downloads will always fail.
## Note on History Access
The Teams bot webhook only delivers **new** messages. Any attempt to fetch **prior messages**, thread history, or message lists requires Microsoft Graph permissions (for example, `ChannelMessage.Read.All` or `Chat.Read.All`). Without Graph, history lookups will always return empty or be unavailable.
## Validation Checklist
- [ ] Teams app installed in target team.
- [ ] Graph permissions added and admin consented.