Verification Center

Track email, domain, identity, and security checks with clear status and recovery actions. The screen connects Checks and Domains so workspace admins can find the “Verify account” action while checking verified users and pending.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Email verification · 98% and Domain verification · 94%, rather than an empty visual shell.

Verification Center
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Verify account

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Verify account” action without losing sight of verified users, pending and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Verify account is clearly available where the task happens.
  • Main view: Checks keeps the starting point obvious.
  • Connected view: Domains supplies nearby context.
  • Metric: Verified users is visible with a meaningful value.
  • Another signal: Pending helps people judge what to do next.
  • Representative record: Email verification · 98% makes the example specific.
  • Second record: Domain verification · 94% shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading checks without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for domains; clarify who can continue.
  • Success after choosing Verify account; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Checks → Domains → Verify account → Review outcome

Patterns used

Workspace, Checks, Domains, Identity, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Email verification · 98% with Domain verification · 94%. Make verified users clear, then use pending to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Verify account” action. The happy path alone is not enough.

Related UI examples: Profile Setup, First Run Checklist, Role Permission Setup.

Start from this in Figr

Design a verification center screen for our existing software product. Use our real design-system tokens, components and product language. Show Checks and Domains, include believable records such as Email verification · 98%, and make verify account easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr