Docs/Audit/Audit Logs — Viewing and Filtering

Audit Logs — Viewing and Filtering

Product version: 1.0.0+1
Last updated: 2026-10-03
Audience: Users with audit:read

A. Viewing Audit Logs

Open the list

Side rail Audit → /audit/logs.

The list is newest-first by default (sortable by Occurred). Pagination uses previous/next controls. Default page size is 10; the table footer lets you choose another rows-per-page value (the server returns at most 100 rows per page).

Table columns

Column Description
Occurred Local date/time when the action happened
Activity Human description when available
Action Colored action badge (CREATE, UPDATE, DELETE, LOGIN, …); a Support access badge marks entries a platform support agent made under a support access grant
Target Entity type + entity id
Actor Avatar, display name, and email / role / id as available; system and webhook events show system

There is no Tenant column — you always see the current organization. On narrow screens the table scrolls horizontally.

Detail

Tap a row to open detail at /audit/logs/detail/:id. The page fetches the log by id (and can reuse in-memory data when you navigate from the list).

Section Contents
Summary Action badge, description, occurred time, severity when present
Actor Name, email, role, copyable user id
Resource Entity type/id, action, changed field names
Context IP, user agent (if present)
Changes Before/after per field when recorded
Technical Request/session ids; expandable JSON (old / new / metadata)

B. Filtering

Control Behavior
Search Debounced free-text search (q) across description, actor email, entity type, and action
Action Single dropdown: CREATE, UPDATE, DELETE, LOGIN, LOGOUT, READ, EXPORT, IMPORT, APPROVE, REJECT
Date range Inclusive calendar range on occurrence date
Clear Clears search, action, and dates

Not in the current UI: multi-select action namespaces, actor autocomplete, dedicated target-id field, filter bookmarks / URL sync.

Use Search to approximate actor email or entity type when those values appear in searchable fields.

C. Tips

  • Narrow with date range first on busy organizations.
  • Combine action + search to find who changed a resource.
  • You can reopen a log later via its detail URL if you still have audit:read for that organization.

Back to: Overview
Related: Roles overview