User Management

Manage workspace users with role, team, access state, authentication, last active date, seat assignment, and bulk admin actions. This example brings Users and Roles together so administrators and growth teams can find the next task without losing context.

It includes representative records such as Maya Chen · Product and Jon Bell · Sales. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

User Management
Use this template in Figr

Template facts

Screen

Table

Primary action

Add user

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

Key elements

  • Main workspace: Users gives users an obvious place to start.
  • Supporting view: Roles keeps the related context close.
  • Primary action: Add user stays visible when people need it.
  • First signal: Users shows a useful value (248).
  • Second signal: Active gives additional context (226).
  • Sample record: Maya Chen · Product.
  • Next record: Jon Bell · Sales.

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

Users → Roles → Add user → Review outcome

Patterns used

Table, Users, Roles, 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 users and roles. People need to distinguish Maya Chen · Product from Jon Bell · Sales. Keep users 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 “Add user”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a user management screen inside our existing product. Use our current components, tokens and content language. Include Users and Roles views, credible records like Maya Chen · Product, and a clear “Add user” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr