Appearance
Watching what is happening now
The live pages: what is in the building at this moment, and what has just gone wrong.
These pages read the live side of the pipeline, so they are current to within seconds. Every report, by contrast, reads rolled-up tables that are rebuilt every five minutes — which is why a report and a page here can disagree about the last few minutes without either being wrong. The ingestion diagram shows why.
Nearly every page below is permission-gated. If a colleague cannot see one, that is their role rather than a fault — Roles is where to look.
Dashboard
/admin/dashboard
The landing page: headline counts for your organisation, recent activity, and the tiles you have chosen to keep.
When you would open it. The five-second answer to "is anything on fire?" before you go looking at a specific page.
Before it has anything on it. Gateways online, or every tile is zero. Two default tiles are easy to misread — Enter / Exit counts crossings, not people inside, and "Visitors" counts devices, not people.
Monitor
Live Monitor
/admin/monitor
A live floor plan with every tracked device drawn on it, moving as positions update.
When you would open it. Watching a space in real time — following someone during a calibration walk, or proving to yourself that a new gateway is doing something.
Before it has anything on it. A venue with a floor plan uploaded and calibrated, and devices actually being seen by its gateways. Positioning needs at least three gateways online; below that, devices fall back to "nearest gateway" and the dots get coarse.
Right Now & Live Alerts
/admin/monitoring/right-now
Every zone with its current occupancy, its status, and the live alert feed beside it.
When you would open it. The page to leave open on a wall screen. It answers "which rooms are in use, which are over capacity, and what has just fired" without a date picker.
Before it has anything on it. Zones drawn, and something in them that counts — a radar, a counting sensor, or tags on the people you care about. A zone with none of those honestly reports nothing.
→ Occupancy: which number is which
Last 24 hours
/admin/report/last-24h
One feed of the last twenty-four hours: counts and events together, newest first.
When you would open it. Working out what happened overnight, or what has been going on since you last looked.
Before it has anything on it. Nothing beyond devices reporting. Note the window rolls — it ends now, so it spans two calendar days and will not match a report run for "today".
Entity Tracker
/admin/monitor/entity
One person or asset at a time: where they have been today, in order, with the zones and times.
When you would open it. Answering "where is this forklift?" or "was this contractor in the plant room?" — the single-subject view, as opposed to the whole-floor view of the Live Monitor.
Before it has anything on it. An entity with a tag assigned to it. Without that you have a MAC address and no name to search for.
Zone occupancy
/admin/monitor/zone-occupancy
A table of every zone with its count, its capacity and how full it is, refreshed as you watch.
When you would open it. The list form of Right Now — better when you have more zones than fit on a plan, and the quickest way to spot a zone whose capacity has never been set.
Before it has anything on it. Capacity set on the zone before "how full" means anything. Without it you get a count and no percentage.
Anomalies
/admin/manage/device/anomalies
Devices that have stopped reporting, are draining their battery unusually fast, or are reporting far less than they used to.
When you would open it. The maintenance queue. Work down it and the rest of the platform stays honest, because almost every "the numbers look wrong" question upstream starts with a device that went quiet.
Before it has anything on it. A device needs enough history for Omaya to know what normal looks like for it. Tags are given a three-day silence threshold, because a tag that is genuinely not moving is not a fault.
Central Alerts
/admin/report/alerts
Every alert the platform has raised, in one feed — rule fires, anomalies and battery warnings together.
When you would open it. Checking what has been raised without opening three pages. Read the kinds differently: a rule fire is something you asked to be told about, an anomaly is the system noticing on its own.
Before it has anything on it. Alerts depend on rules existing and sensors reporting, so an empty feed can mean nothing is wrong or that nothing is watching. It is worth knowing which.
OAIA
/admin/oaia
The Omaya AI assistant: a periodic written briefing on what changed, plus a place to ask questions of your own data in plain language.
When you would open it. Instead of reading six reports to find the one thing that moved. It writes only when something has actually changed, so a quiet day produces a short note.
Before it has anything on it. Nothing, to start: the detectors run and notify with or without an AI provider. A key for your organisation is what adds the prose and the chat. The interval is yours to set — 2, 4, 6, 8, 12 or 24 hours.
This list is read from the admin menu itself, so it cannot fall behind it.