Logs
The platform audit trail — who did what, when, and from where. Read it when you need to explain a change rather than guess at one.
What it records
Logs capture consequential actions across the platform — sign-ins, role and permission changes, organisation and licence changes, destructive operations and bulk imports. Each entry carries the actor, the affected record, a timestamp and the originating context.
- This is an audit trail, not application debug output. It answers "who changed this and when", not "why did the server error".
Using it well
- Filter by actor when investigating a specific user’s activity.
- Filter by date range first — it is the cheapest way to cut a large trail down.
- Cross-check a suspected permission change against Roles & Permissions; the log tells you when it happened, that screen tells you the current state.
- Treat the trail as evidence: read it before making corrective changes, because your own corrections become entries too.