Read the log
Entries are newest first, and the page refreshes every 30 seconds. Each entry shows what was changed, the action (Created, Updated, Deleted or Submitted; any other kind of action, such as a data export or an asset import, reads Action), who did it and when. Expand an entry to see exactly what changed: a field-by-field comparison of before and after. Secrets, such as device passwords and token values, are never recorded. Entries for data requests, such asprivacy.access_export and privacy.erase, show the person who did it as user: followed by an ID, not their name or email. People who’ve been erased appear in older entries as a stand-in such as erased-user-1a2b3c4d. If your organisation is offboarded, the log also shows customer.offboard and customer.offboard_cancel entries.
One device’s history
Every device page has an Activity button showing just that device’s history: edits, and every command sent to it, with who sent it.Keep or analyse the log elsewhere
The page shows the latest 100 entries. For the full history, a longer retention, or to feed a SIEM, read the log through the Public API with a token that has the Read audit log scope. The API can filter by action, kind of record, record, person and date range. It can also filter by device, room, building or location, each including everything in it: its devices, their commands, assets and Room Readiness runs. For a rolling window, such as the last 15 minutes, uselast=15m. See List audit entries.
How long it’s kept
The audit log is kept for 24 months, then deleted.Updated 06 Nov 2026 14:07 · page 14f6839