how it works

One authorization. Then the canary takes the watch.

A Full Admin connects OmniCanary read-only in minutes. From then on, your organization is re-examined continuously — and every finding is written up so anyone can act on it.

Three steps. The first one is the only one you do.

step 01

Connect, read-only

A Full Admin authorizes our read-only Service App from Control Hub. Minutes, not a project — no write scopes, nothing installed.

step 02

We mirror and sweep

OmniCanary keeps a complete mirror of your org — people, licenses, devices, workspaces, locations, trunks — and re-examines it every day against 14 curated policies.

step 03

You read findings, not dashboards

Each issue says what's wrong, why it matters, and what fixing it does. Act in Control Hub — or, if you later opt in, with a previewed one-click fix.

the connect wizard

Two stages. Only the first is required.

stage 1 · required · minutes

Read-only sync

Your Full Admin authorizes the read-only Service App from Control Hub. The wizard waits for Webex's own confirmation, runs the first full sync with visible progress, and your first findings are on screen at first login.

stage 2 · optional · whenever, or never

One-click fixes

A separate app with write permission, authorized only if you choose to enable fixes. Until then the capability doesn't exist for your organization — there is nothing to switch on by mistake.

the watch

Around the clock, sized to your organization.

Small and mid-sized organizations are re-listed every 15–30 minutes. Very large ones get a complete nightly pass plus change-hints during the day — and device telemetry paces itself to your fleet.

tonight's watch acme corp · 10,842 people
02:00directory re-listed — 10,842 peoplecomplete
02:31device sweep — 456 devices3 offline
04:00deep reconciliationcomplete
06:0014 policies evaluatedcomplete
06:003 new findings, written in plain language
in a hurry? “Scan now” re-checks your whole org on demand.
the honesty rules

The data can't lie to you.

No false resolutions

An issue resolves only after a complete, authoritative re-check of every dataset the policy reads. Stale or partial data can never mark anything healthy.

Unsupported is unsupported

A device without a sensor shows as unsupported — never as a healthy zero. Capability gaps are stated, not papered over.

Freshness on every number

Every count carries its own as-of stamp. If coverage goes stale, you see that — the dashboard never silently trusts old data.

See what your org has been trying to tell you.

Pilots are set up personally, with a Webex specialist — not a signup form. Connect read-only, run the first scan, and keep the findings either way.

support@omnicanary.com