Usage analytics carries per-person activity, so it stays with the person who runs the platform. You'll be back on the desktop in a moment.
Usage analytics
How the hub is being used — collected since —, day boundary AEST
DEMO DATA
Include internal
0 online
Nobody on the hub right now
📡
Telemetry is armed
Data appears here as staff use the hub — engaged time, tools opened, devices, peak hours.
Check back after the team's next working day. Append ?demo=1 to preview with sample data.
Daily activity
bars = active people · line = engaged hours
When the hub is used
engaged time by weekday × hour
Tool leaderboard
People
Report regions
engaged time by region opened
Devices
sessions by browser / viewport width
First tool of the day
what people open first, beyond the hub
Errors
uncaught JS errors (client_errors)0
—
—
How this is measured. Every signed-in page carries a lightweight collector
(shared/pp-telemetry.js). A second counts as engaged only while the tab is visible and the
person gave any input in the last 60 seconds (5 minutes during fullscreen presenting) — the same
engagement model GA4 uses. Beats flush once a minute into one row per person, tool and AEST day; nothing is
recorded per keystroke or per click, no content is captured, and exports, embeds and the PDF renderer are
excluded at source. Internal traffic (the dev account, the test account, the PDF service account)
is included by default — untick “Include internal” to see staff-only numbers. Reading this data is
triple-locked to the dev role: RLS on the table, a role check inside the RPCs, and this page's own gate.