Who can add Omni to a workspace?
A workspace administrator installs Omni. After that, channel membership decides who meets it: Omni answers in the channels it has been added to, not everywhere at once.
Omni Companion
Omni, in the channel.
Answers, actions and approvals where the work already happens.
01 · Channel
A conversation, not a second inbox.
Omni sits in the channel the team already uses. The answer cites the source, and the action waits for the person who owns it.
Illustration of Omni Companion in a Slack channel called finance-ops: a question about a duplicate invoice, an answer citing Refund policy v4, a drafted credit note and an approval waiting on the owner.
02 · Answers
Every answer shows its source.
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
A channel sees what its members can already open. A conversation in one channel cannot widen another, and knowledge does not leave the workspace.
03 · Actions
The answer becomes the action.
A question can end in a run, not another tab.
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 · Controls
The controls stay with the workspace.
Install, membership and the record are part of the workspace you already govern.
Workspace install
An administrator installs Omni into the workspace. It does not arrive in a channel uninvited.
Channel membership
The people in the channel are the people who meet Omni. Identity maps to the same Omni account as the rest of the suite.
Audit
Every answer and every action is on the record, with an approval trail and an export to your own store.
05 · FAQ
Questions before the install.
Three that come up before Omni reaches a channel. Anything else belongs in the scoping call.
Does it read private channels?
Only channels it has been added to, and only what the reader can already open. Permission follows the source, so a private channel never becomes a shortcut around it.
What gets logged?
Every answer with its question, sources and timestamp; every action with its target and result; every approval with who approved and when. A signed export goes to your own store or SIEM.
Continue
The rest of the suite.
Pilot · 3–5 owners
Put Omni in one channel.
Start with the channel where the repeated questions live. Bring the tools and the documents behind them, and we will show you what Omni does with the thread.