Archive & Restore

Review archived files and projects with retention dates, owners, size, and safe restore or permanent-delete actions. This example brings Archived and Recently archived together so content and product teams can find the next task without losing context.

It includes representative records such as 2025 launch archive and Old research repository. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Archive & Restore
Use this template in Figr

Template facts

Screen

Table

Primary action

Restore selected

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 selected while keeping archived, expiring soon and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Archived gives users an obvious place to start.
  • Supporting view: Recently archived keeps the related context close.
  • Primary action: Restore selected stays visible when people need it.
  • First signal: Archived shows a useful value (284).
  • Second signal: Expiring soon gives additional context (22).
  • Sample record: 2025 launch archive.
  • Next record: Old research repository.

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

Archived → Recently archived → Restore selected → Review outcome

Patterns used

Table, Archived, Recently archived, 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 archived and recently archived. People need to distinguish 2025 launch archive from Old research repository. Keep archived 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 selected”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Folder Permissions, Document Detail, Template Gallery.

Start from this in Figr

Design a archive & restore screen inside our existing product. Use our current components, tokens and content language. Include Archived and Recently archived views, credible records like 2025 launch archive, and a clear “Restore selected” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr