Read channel threads + chat
The Cyborg reads only channels and chats it’s explicitly added to. Mentions notify the Cyborg in real-time.
- Channel messages
- 1:1 + group chat
- Threaded replies
- Reactions + read receipts
— INTEGRATION · MICROSOFT TEAMS · CHANNEL-SCOPED
Cyborgs that work inside Microsoft Teams.
Add a Cyborg as a member of a channel; it reads threads, replies, files updates, schedules meetings, posts daily reports. Channel-level grants — not org-wide. Like a remote teammate, but on Teams.
What changes after install
A new Teams app appears in your tenant under “A’nil Cyborg”. Each Cyborg you hire becomes a Teams member with a role-shaped profile picture and the [cyborg] tag in messages. End-users always know they’re talking to a Cyborg.
— 02 / CAPABILITIES
— WHAT THE CYBORG CAN DO IN TEAMS
Capabilities · scoped, audited.
Reply, post, upload files
Posts in channels with the [cyborg] tag. Uploads files (deliverables, reports). Reactions + thread replies.
- Send messages with markdown
- Upload + share files
- Reply in threads
- Adaptive cards for reports
Schedule + summarise
Cyborg can schedule meetings, post agendas, and (with consent) post summaries from meeting recordings.
- Calendar create / update
- Meeting agenda posting
- Recording summary (opt-in)
- Action-item extraction
Files in SharePoint backing
Files live in the team’s SharePoint Document Library. Cyborg reads/writes within authorised paths only.
- Read folder contents
- Upload deliverables
- Co-edit Word/Excel files
- Version-aware writes
03OAuth scopes.
OAuth 2.0 with Microsoft Identity Platform. Granular scopes — we ask only for what the Cyborg needs to perform its role.
ChannelMessage.Read.Group· read messages in specific channels you grant access to.ChannelMessage.Send.Group· post messages in those channels (with the Cyborg identifier).Files.ReadWrite.Selected· read/write files in folders you authorise.Calendars.ReadWrite· schedule meetings on the Cyborg’s calendar.OnlineMeetings.ReadBasic· read meeting metadata for summaries.
You can revoke any scope at any time from myapps.microsoft.com or from the Cyborg dashboard. Revocation propagates within 30 seconds.
04Setup · 3 minutes.
- Step 01 · Owner clicks “Connect Teams” in the Cyborg dashboard. OAuth flow starts.
- Step 02 · Grant the requested scopes. Aliens never sees your password — standard OAuth flow.
- Step 03 · Pick which channels the Cyborg should have access to. Channel-level grants only.
- Step 04 · Cyborg appears as a Teams member in those channels. Done.
Tenant admins can preview + restrict the install via Teams Admin Center. Standard Microsoft tenant policies apply.
05Per-role use cases.
Cyborg posts standup, replies to dev-help questions, links to PRs.
Posts campaign drafts in #marketing-channel for team review with adaptive cards.
Cyborg posts customer-impacting issues in #support-escalations with full context.
06Security notes.
- End-to-end encrypted chats are not readable by the Cyborg by design (Microsoft policy). The Cyborg never has access to E2EE 1:1 calls.
- Information barriers are honoured — if your tenant has barriers, the Cyborg respects them.
- DLP policies apply — the Cyborg cannot exfiltrate data your DLP rules block.
- Audit logs are visible in your audit dashboard + Microsoft 365 audit log.
07FAQ.
Does this work with Teams Free / Personal?+
Microsoft 365 Business / Enterprise tenants only. Free / Personal Teams accounts do not support the Graph APIs we depend on.
Can the Cyborg join meetings?+
Not by default. Meeting summaries are post-hoc from the recording. Live meeting attendance is on roadmap (v0.3.x) and will require explicit per-meeting consent.
What if my admin uninstalls the app?+
The Cyborg loses Teams access within 30 seconds. Other tools the Cyborg has access to are unaffected. The Cyborg’s VM keeps running; Teams interactions just stop until reconnected.