Overview
Modus reads Teams channels and conversations so decisions made in Teams reach your agents, and routes human approvals back into Teams where your people already are.
What Modus reads
- 1Team
- 2Channel
- 3Message thread
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
2context types mined
4agent tool groups
1connection method
5security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Channel context
Teams, channels, and conversation history the connection is permitted to read.
Membership context
Team and channel membership, so attribution is accurate.
Example context item
teams_channel_contextRevenue Ops›General
- Members
- 37
- Recent thread
- Q3 forecast methodology change
- Approval route
- Human approvals delivered to this channel
Common use cases
- 01
Route every write approval to the channel that owns the system being changed.
- 02
Capture a decision made in Teams into the governed context layer.
- 03
Let an agent post a governed answer back into the channel that asked.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
OAuth (managed)
Managed OAuth against a Teams bot registration in your tenant.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Permission mirroring
Tool calls execute as the person asking, not as a shared workspace credential, so an agent can never reach a channel or file the user cannot.
Write approval
Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
