Version History

Review every saved version with author, timestamp, change summary, restore point, and comparison context. This example brings Versions and Compare together so content and product teams can find the next task without losing context.

It includes representative records such as v38 · Pricing copy edits and v37 · Permission edge cases. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Version History
Use this template in Figr

Template facts

Screen

Table

Primary action

Restore version

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to restore version while keeping versions, contributors and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Versions gives users an obvious place to start.
  • Supporting view: Compare keeps the related context close.
  • Primary action: Restore version stays visible when people need it.
  • First signal: Versions shows a useful value (38).
  • Second signal: Contributors gives additional context (7).
  • Sample record: v38 · Pricing copy edits.
  • Next record: v37 · Permission edge cases.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Versions → Compare → Restore version → Review outcome

Patterns used

Table, Versions, Compare, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to versions and compare. People need to distinguish v38 · Pricing copy edits from v37 · Permission edge cases. Keep versions visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Restore version”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Media Upload, Publishing Workflow, Asset Library.

Start from this in Figr

Design a version history screen inside our existing product. Use our current components, tokens and content language. Include Versions and Compare views, credible records like v38 · Pricing copy edits, and a clear “Restore version” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr