Bulk User Import

Import many users from CSV with field mapping, role assignment, duplicate handling, validation errors, invite behavior, and a final review step. This example brings Upload and Map fields together so administrators and growth teams can find the next task without losing context.

It includes representative records such as Upload CSV and Map email and name. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Bulk User Import
Use this template in Figr

Template facts

Screen

Form

Primary action

Import users

Pattern

Form

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 import users while keeping rows, valid and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Upload gives users an obvious place to start.
  • Supporting view: Map fields keeps the related context close.
  • Primary action: Import users stays visible when people need it.
  • First signal: Rows shows a useful value (248).
  • Second signal: Valid gives additional context (236).
  • Sample record: Upload CSV.
  • Next record: Map email and name.

States worth designing

  • Required field missing: say what changed, protect progress, and offer a clear next step.
  • Invalid value or incompatible data: say what changed, protect progress, and offer a clear next step.
  • Draft saved: say what changed, protect progress, and offer a clear next step.
  • Submitted for review: say what changed, protect progress, and offer a clear next step.
  • No permission to submit: say what changed, protect progress, and offer a clear next step.
  • Temporary save failure: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Upload → Map fields → Import users → Review outcome

Patterns used

Form, Upload, Map fields, contextual actions, error recovery

Why these choices work

Show requirements beside fields and retain values after failed checks. Validate only the affected input and make the next step unmistakable.

Pay attention to upload and map fields. People need to distinguish Upload CSV from Map email and name. Keep rows 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 “Import users”. Make error recovery as clear as the happy path.

Related screen examples to explore next: User Management, Data Export Center, Webhook Settings.

Start from this in Figr

Design a bulk user import screen inside our existing product. Use our current components, tokens and content language. Include Upload and Map fields views, credible records like Upload CSV, and a clear “Import users” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr