Book a scoping call

Security

Your infrastructure. Your rules.

Residency, permissions, approvals and an audit trail for every answer and every action.

Request the security packSee licensing

01 · Surfaces

Three surfaces, one boundary.

Home, Concierge and Companion sit on the same identity, the same permission rule and the same record.

Home

Who
Your team, on the same account as the rest of the suite.
Identity
Single sign-on, groups and roles from your directory.
Data boundary
Team knowledge stays inside the tenant boundary.
Control
Permissions mirror the source. Every answer cites the page and the timestamp.

Concierge

Who
Customers, suppliers and external counterparts.
Identity
A named external identity, scoped to the conversation.
Data boundary
Customer and supplier access stays inside the same boundary.
Control
Commitments can wait for an approver. Handoff to a person when the thread needs one.

Companion

Who
The people already in Slack, Teams or Mattermost.
Identity
The channel identity maps to the same Omni account.
Data boundary
The room stays inside the workspace you already govern.
Control
Approvals and audit follow the conversation. Writes can require a human.

02 · Residency

Where the data lives.

The deployment decides the boundary. The platform does not move knowledge anywhere you did not put it.

On-prem keeps everything in your building. Private cloud keeps it in an account and region you choose. Hybrid draws the line per service, so knowledge can stay on-prem while a model route runs privately. Air-gapped runs with no outbound link; updates arrive as a signed offline bundle.

The boundary in each mode

On-prem, private cloud and air-gapped. In each mode, Omni Core, Knowledge, Models and Tools sit inside your network. External tools stay outside the boundary, and in the air-gapped mode there is no outbound link.01Your networkKnowledgeModelsToolsOmni CoreExternal toolsCRMFinanceData02Your networkKnowledgeModelsToolsOmni CoreExternal toolsCRMFinanceData03Your networkKnowledgeModelsToolsOmni Coreno linkExternal toolsCRMFinanceData

  • 01On-prem

    Runs on your hardware, inside your network.

  • 02Private cloud

    Runs in a private cloud account you control.

  • 03Air-gapped

    Runs with no internet connection.

The boundary is the same in every mode: Omni Core, Knowledge, Models and Tools stay inside your network.

03 · Permissions

Permission travels with the source.

Knowledge permissions mirror the source system. The answer cannot be wider than the reader's access.

The rule

If you cannot open it, Omni will not quote it.

Source
The document, page and version behind the answer, named in the answer.
Timestamp
When the source was read, so a changed page is visible as a changed answer.
Permission
The reader's access to the source, checked before the answer is given.

04 · Audit

Every answer. Every action.

The record is written as the work happens, not reconstructed afterwards.

  1. Every answer

    The question, the sources, the model route and the timestamp are written to the record.

  2. Every action

    The write, the target, the result and the person or rule behind it are logged.

  3. Approval trail

    Who approved, when, and what changed after the approval.

  4. Export

    A signed export to your own store or SIEM, on your schedule.

05 · Approvals

A human can be the last step.

The default is useful. The exception is permission: when the action is a commitment, the run can wait.

Writes can require a human

A create, update or send can pause for a named approver before it happens. The run waits; it does not guess.

Concierge commitments

Prices, dates and promises to a customer or supplier can require approval before the answer leaves the room.

Handoff to a person

When the thread needs judgement, Omni hands it to a person with the context and the sources attached.

06 · Operations

The controls around the platform.

Identity, keys, recovery and updates are part of the deployment, not a later add-on.

SSO and SCIM

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.

Encryption

At rest and in transit, with keys held in your environment.

Backup and restore

A documented path for knowledge, configuration and audit records.

Signed updates

Updates arrive signed and roll back to the previous release if they fail.

HA and disaster recovery

Redundant data stores and a recovery plan for Enterprise deployments.

07 · Procurement

The pack you can send to procurement.

The security review and the commercial review run together. Ask for the pack and we will scope it to your process.

For the reviewer

Start with the boundary.

Tell us the deployment mode and the reviewers who need to sign. We will send the security summary, the deployment checklist and the DPA or SLA your process requires.

Request the security pack
  • Security summary — The boundary, identity model, permission rule and audit path in one document.
  • Deployment checklist — Hardware, network, identity, backup and recovery prerequisites for your platform team.
  • DPA and SLA on request — Reviewed with your legal and service owners before the order.

Continue

Procurement

Send the pack to your reviewer.

The security summary, the deployment checklist and the DPA or SLA are available on request. Tell us what your process needs and we will send the right documents.

Request the security packSee licensing