Audit Log Table
Append only security log with mono timestamps, actor avatars, code chip action keys, targets, and source IPs.
Append only security log with mono timestamps, actor avatars, code chip action keys, targets, and source IPs.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Audit Log Table is the security record every workspace settings page legally needs: mono timestamps down to the second (Jun 12, 14:02:11), the actor with their avatar, the action as an inline code chip (key.created, member.removed, billing.plan_changed), the target of the action, and the source IP in mono tabular figures. Six entries span two days of real Acme workspace activity. The footer is the policy and the point: entries are append only, and even admins cannot edit this table.
Entries are one array. The code chip style on actions lets ops staff scan event types without reading full sentences, which is exactly the shape security tooling expects.
Reach for this block on the workspace security or audit page, wired to your audit log endpoint with cursor-based pagination. Restrict access to Owner and Admin roles at the route level before wiring the export button.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the workspace security audit log. Other audit tables:
Tip: the append-only guarantee is worth stating in the footer; it turns a table into a trust signal.