Account Creation

Create an account with clear requirements, workspace naming, region, and access defaults. The screen connects Account and Workspace so workspace admins can find the “Create workspace” action while checking completion and email verified.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Create account and Verify email, rather than an empty visual shell.

Account Creation
Use this template in Figr

Template facts

Screen

Form

Primary action

Create workspace

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Create workspace” action without losing sight of completion, email verified and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Create workspace is clearly available where the task happens.
  • Main view: Account keeps the starting point obvious.
  • Connected view: Workspace supplies nearby context.
  • Metric: Completion is visible with a meaningful value.
  • Another signal: Email verified helps people judge what to do next.
  • Representative record: Create account makes the example specific.
  • Second record: Verify email shows the pattern works beyond one item.

States worth designing

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading account without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for workspace; clarify who can continue.
  • Success after choosing Create workspace; 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

Account → Workspace → Create workspace → Review outcome

Patterns used

Form, Account, Workspace, Team, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Create account with Verify email. Make completion clear, then use email verified 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 “Create workspace” action. The happy path alone is not enough.

Related UI examples: Workspace Onboarding, Team Invitation, SSO Setup.

Start from this in Figr

Design a account creation screen for our existing software product. Use our real design-system tokens, components and product language. Show Account and Workspace, include believable records such as Create account, and make create workspace easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr