Who can add Omni to a team?
A Teams administrator installs Omni for the organisation. Channel membership then decides who meets it, and the same identity and roles apply as the rest of the suite.
Omni Companion
Omni, inside Microsoft Teams.
The same agent, across your Microsoft estate.
01 · Channel
Finance, in the thread.
Omni sits in the team the work already happens in. The answer cites the workbook; the approval waits for the owner.
Illustration of Omni Companion in a Microsoft Teams channel called Finance: a question about the quarterly forecast, an answer citing the SharePoint workbook and its refresh time, and an approval waiting on the owner.
02 · Answers
Answers with the source attached.
The same knowledge and the same permission rule as the rest of Omni, quoted where the question was asked.
The rule
If you cannot open it, Omni will not quote it.
Cited
The document, page and version behind the answer, named in the reply. The timestamp says when the source was read.
Permitted
The reader's access to the source is checked before the answer is given. If you cannot open it, Omni will not quote it.
Contained
The room stays inside the team you already govern. A conversation in one channel cannot widen another, and knowledge does not leave the tenant.
03 · Actions
Actions with an approver.
A question can end in a run, and a run can wait for a person.
Run a tool action
A connected system can be read or written from the thread, through the same connection layer as the rest of Omni.
Require approval
A write can pause for a named approver before it happens. The run waits; it does not guess.
Turn a thread into a workflow
A question that keeps coming back can become a workflow, with a trigger, branches and a run history.
04 · Microsoft
One agent across the estate.
Teams is the room. The context comes from the rest of the Microsoft estate, under the same permission rule.
Teams
Questions, answers and approvals in the channel, with the same identity and the same roles as the rest of the suite.
SharePoint
Documents and pages are read with the reader's permission, then cited with the version and the time they were read.
Outlook and Exchange
The message or meeting that started the thread travels with it, resolved to the same identity and the same permission rule.
05 · Controls
The controls you already run.
Identity, roles and the record are part of the deployment, not a later add-on.
Single sign-on
Sign-in through your identity provider, with directory-driven joiner, mover and leaver flows.
Roles
Administrator, builder, approver and reader roles, scoped to the team and the source.
Audit
Every answer and every action on the record, with an approval trail and an export to your own store or SIEM.
06 · FAQ
Questions before the install.
Three that come up before Omni reaches a team. Anything else belongs in the scoping call.
Where do the answers come from?
From the knowledge you have connected, read with the same permission rule as the rest of Omni. Every answer names the source and the time it was read.
What gets logged?
Every answer with its question, sources and timestamp, every action with its target and result, and every approval with who approved and when. The record can be exported to your own store or SIEM.
Continue
The rest of the suite.
Pilot · 3–5 owners
Start in one team.
Pick the team where the repeated questions live. Bring the site, the workbook and the exception that keeps breaking, and we will show you what Omni does with the thread.