Document Detail

Inspect a document with owner, status, sharing, activity, comments, linked work, and version context around the content itself. This example brings Overview and Activity together so content and product teams can find the next task without losing context.

It includes representative records such as Product requirements v3 and Stakeholder feedback. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Document Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Edit document

Pattern

Detail

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to edit document while keeping views, comments and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Activity keeps the related context close.
  • Primary action: Edit document stays visible when people need it.
  • First signal: Views shows a useful value (184).
  • Second signal: Comments gives additional context (14).
  • Sample record: Product requirements v3.
  • Next record: Stakeholder feedback.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Activity → Edit document → Review outcome

Patterns used

Detail, Overview, Activity, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to overview and activity. People need to distinguish Product requirements v3 from Stakeholder feedback. Keep views 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 “Edit document”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Archive & Restore, Folder Permissions, Template Gallery.

Start from this in Figr

Design a document detail screen inside our existing product. Use our current components, tokens and content language. Include Overview and Activity views, credible records like Product requirements v3, and a clear “Edit document” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr