Audit log

The audit log is who did what, and whether it succeeded. It is kept for one year. Device readings are not listed here.

Who can see it

• A tenant owner or tenant admin sees that tenant only.
• A site user does not see the tenant audit.
• The platform owner sees every tenant under Platform admin → Audit, including a failed login that could not be tied to a tenant.

Where it appears

• Home → Recent activity is the short list for an owner or admin.
• Account → Audit log is the full search: time range, entity type, action, status, and a text search on the user, the name, or the id. From and to are optional. The list has a page size. Times show the timezone that is on the clock.
• Open a row to read the request detail. Passwords, tokens, and secrets are not stored.

What is recorded

Creates, updates, and deletes. Attribute writes. Commands. Alarm acknowledgement and clear. Login, logout, a failed login, login-as, and a password change. Cancelling a firmware update is Cancelled, with the firmware title and the device name. A profile update that changes an alarm rule includes the rule name. When an integration stops being the default, the audit names it. Deleting the default records that none remains. A delete keeps the name that was on the screen, including a device profile, so Recent activity still shows that name after the row is gone. Home recent activity uses the same timezone label.

A failed audit write does not undo the action that already succeeded.

What is not recorded

Telemetry ingest, telemetry queries, analytics, and rule-engine preview. A wrong meter reading is not an audit row. The reading stays in telemetry. The audit row is the person who changed a device, a user, a dashboard, or an alarm.