Data Export Center

Create and monitor data exports with dataset, filters, format, size, requester, status, expiry, and download history. This example brings Exports and Scheduled together so administrators and growth teams can find the next task without losing context.

It includes representative records such as All customer accounts · CSV and Audit log · September. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Data Export Center
Use this template in Figr

Template facts

Screen

Table

Primary action

New export

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to new export while keeping exports this month, ready and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Exports gives users an obvious place to start.
  • Supporting view: Scheduled keeps the related context close.
  • Primary action: New export stays visible when people need it.
  • First signal: Exports this month shows a useful value (42).
  • Second signal: Ready gives additional context (8).
  • Sample record: All customer accounts · CSV.
  • Next record: Audit log · September.

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

Exports → Scheduled → New export → Review outcome

Patterns used

Table, Exports, Scheduled, 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 exports and scheduled. People need to distinguish All customer accounts · CSV from Audit log · September. Keep exports this month 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 “New export”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Bulk User Import, Webhook Settings, User Management.

Start from this in Figr

Design a data export center screen inside our existing product. Use our current components, tokens and content language. Include Exports and Scheduled views, credible records like All customer accounts · CSV, and a clear “New export” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr