Interface Lab
Back to knowledge
Design Systems Page Patterns

Audit Log Timeline

Audit Log Timeline turns a frequent interface judgment into an executable constraint before generation.

Design Principle

Audit logs need to answer who, when, what object, what action, and what impact.

Principle

Audit logs need to answer who, when, what object, what action, and what impact.

Design action

Timeline items show actor, action verb, object, diff, source IP/system, and filters; high-risk events stand out without hiding ordinary events.

Examples

Positive example: Permissions, billing, moderation, design system changes, and data export need traceability. Counterexample: Logs only say updated without object or diff.

Apply when

Permissions, billing, moderation, design system changes, and data export need traceability. Users need to judge state, scope, risk, or next action quickly.

Source notes

Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/

Agent Directive

Timeline items show actor, action verb, object, diff, source IP/system, and filters; high-risk events stand out without hiding ordinary events.