SIGNALS Docs
Exit Reader View
100%
Theme

Reader View

Action Log

Browse and export the auditable action trail — users, agents, API callers and automation — with filters and value diffs.

Overview

Action Log is the UI for the audit trail — who (or what) did what, when, with before/after JSON values. Entries are written when actions fire AuditableEvent, whoever the actor was: humans in the web UI, AI agents (MCP tooling), API callers, workflows, plugins, and the system itself. Each row carries a typed actor badge; the actor-type filter narrows to one kind, or to every non-human kind at once.

It is a read surface beyond retention configuration. Deciding whether an action stands is the job of the record it touched — nothing is approved, reverted, or dispositioned here.

Where it lives

Route: /admin/settings/action-log (admin.settings.action-log)

Open Admin → System → Action Log. Sidebar requires action-log.view. /admin/settings/agent-activity redirects here.

Key workflows

  • Filter by action, entity type, actor type (including an "All non-human" option), user name, and date range (URL-synced)
  • The Record column links to the audited record when that entity has a show page; the Change column gives a one-line "field: original → new" summary
  • Expand rows for original/new values, IP address, actor ID, and user agent
  • Export CSV queues ExportActionLog with current filters
  • Pagination: 25 per page, newest first

Logs are pruned on a schedule based on retention (see system configuration). Action Log history is therefore retention-bounded: after pruning, entity history endpoints return only retained entries and expose the boundary in meta.retention; for relational rows without a creation timestamp, the same boundary means retained evidence begins at or after the cutoff. These flags describe an evidence limitation, not proof that a specific deleted row existed, and do not imply an indefinite or complete audit timeline.

This is separate from immutable event-sourced temporal history. Supported event-sourced aggregates retain their Verbs event stream independently of the Action Log projection. Use GET /api/v1/action_logs/state for point-in-time replay when high-confidence temporal state is required after Action Log pruning.

At a glance

Browse the audit trail of all recorded actions — by humans in the web UI, agents, API callers, workflows, plugins, and the system itself. The log captures who (or what) did what, when, and the before/after values for changes. Entries are created automatically when action classes fire AuditableEvent. Requires action-log.view.

The table supports filtering by action type, entity type, actor type (including an "All non-human" option), user, and date range. Each row shows a typed actor badge, a link to the audited record when it has a show page, and a one-line change summary; expand a row for the full original and new value diff. Entries are paginated and sorted by most recent. The /admin/settings/agent-activity URL redirects here.

Action logs are automatically pruned based on the configured retention period (default: 12 months). The signals:action-log:prune Artisan command runs daily via the scheduler.