Appearance
Administration
Who can do what, what the platform has been doing, and the settings that change how it behaves.
Everything here is scoped to your own organisation. Cross-tenant equivalents exist for whoever operates the platform, on a menu you will not see.
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.
System
Admins
/admin/system/admin
The administrator accounts for your organisation, and the role each one holds.
When you would open it. Adding and removing colleagues, and resetting access.
Roles
/admin/system/role
Roles, and the individual permissions each role grants.
When you would open it. Deciding who sees what. Almost every menu item is permission-gated, so a colleague reporting a missing page is usually a role question rather than a fault.
Activity Log
/admin/activity
A read-only timeline of what administrators have done, with a summary strip above it.
When you would open it. Answering "who changed this?" and satisfying an auditor.
SLA & Uptime
/admin/system/uptime
Your organisation’s service levels: uptime, how often rules fired, and where the gaps were.
When you would open it. Reporting against an SLA. Every figure is scoped to your own organisation.
Configuration
/admin/config
Your organisation’s settings in one place: profile and branding, timezone and date format, IoT defaults, indoor positioning tuning, data retention, licence, starter packs and the AI assistant.
When you would open it. The page behind most "why does it behave like that?" questions. Two settings are worth knowing about: data retention, which decides how far back any report can look, and detection speed, which trades how quickly a tag is shown in a new place against how often it flickers between two.
Schedule Report
/admin/system/schedule-report
Reports emailed on a schedule, to a list of people, as PDF or spreadsheet.
When you would open it. The weekly Monday-morning figure that nobody has to remember to run.
Usage
/admin/usage
What your organisation is consuming: devices, messages sent, AI calls, storage — against whatever your licence allows.
When you would open it. Checking headroom before a rollout, and finding out which channel is responsible for a message bill.
Labels
/admin/system/tag
Free-form labels you can attach to venues, zones, gateways, devices and entities.
When you would open it. Cutting across the hierarchy — marking everything installed in one phase, or everything a particular contractor maintains, then filtering on it.
This list is read from the admin menu itself, so it cannot fall behind it.