Seat Management

Manage paid seats, assignments, pending invites, available capacity, and renewal impact for a team subscription. This example brings Seats and Members together so account administrators can find the next task without losing context.

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

Seat Management
Use this template in Figr

Template facts

Screen

Settings

Primary action

Add seats

Pattern

Settings

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to add seats while keeping paid seats, assigned and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Seats gives users an obvious place to start.
  • Supporting view: Members keeps the related context close.
  • Primary action: Add seats stays visible when people need it.
  • First signal: Paid seats shows a useful value (24).
  • Second signal: Assigned gives additional context (21).
  • Sample record: Maya Chen · assigned.
  • Next record: Jon Bell · assigned.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Seats → Members → Add seats → Review outcome

Patterns used

Settings, Seats, Members, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to seats and members. People need to distinguish Maya Chen · assigned from Jon Bell · assigned. Keep paid seats 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 seats”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Billing History, Credit Balance, Usage Metering.

Start from this in Figr

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

Open Figr