UI DESIGN LAB
  • Home
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
Back to knowledge
Design Systems Page Patterns

Audit Log Timeline

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

audit-logtimelineadmin

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.

Agent Directive

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

Apply When

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

Avoid

  • Logs only say updated without object or diff.
  • Irrelevant structure, copy, or decoration is added only to make the UI feel richer.

Knowledge Metadata

Category
Design Systems Page Patterns
Quality
86%
Version
v1
Published
6/6/2026