Key
Doors
locked
unlocked
open
forced / held / offline
locked out
Areas
armed
disarmed
can’t arm
alarm
Gauge
ring = doors secure · shield = armed
| Centre | Since | Severity | Condition | What | Detail |
History
| Centre | When | Severity | Condition | What | Detail |
Inception keeps a separate user record per panel, matched here by name. The strip shows one dot per centre — filled where the person has a record, hollow where they don't.
An empty Card column does not mean no credential. The panel API never returns a security PIN — it can be set from here but never read back — so somebody who badges in with a PIN every day shows nothing in that column.
| Name | Centres | Coverage | Card numbers | Actions |
| Press “Load / refresh” to read cardholders from every centre. |
| Centre | When | Event | Who | What |
| Press “Load” to pull the review log from every centre. |
| Choose a report and press “Run”. |
| Centre | Panel URL | Auth | Connection | Actions |
These are logins for this console, separate from the users on your Inception panels. A manager assigned to specific centres can only see and control those centres — everywhere in the app and in the API.
| Operator | Role | Centres | Last sign-in | Actions |
Panel versions
The Inception REST API exposes protocol version, not firmware version, and cannot perform firmware updates or database backups — those are per-panel web-UI jobs. The links below open the right page on each controller.
| Centre | Protocol | Status | Serial | On the panel |
Not a panel backup. This records the configuration that changes day to day — cardholders, cards, permissions, expiry — through the REST API, so you can see who had access to which centre on any date and rebuild cardholders if a panel is replaced. A restorable controller image still has to come from each panel's own System → Backup/Restore page.
| Taken | By | Contents | Size | Actions |