Profile Setup

Set identity, timezone, role, and notification defaults without burying important choices in settings. The screen connects Profile and Preferences so workspace admins can find the “Save profile” action while checking profile complete and avatar set.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Personal details and Team role, rather than an empty visual shell.

Profile Setup
Use this template in Figr

Template facts

Screen

Form

Primary action

Save profile

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 “Save profile” action without losing sight of profile complete, avatar set and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Save profile is clearly available where the task happens.
  • Main view: Profile keeps the starting point obvious.
  • Connected view: Preferences supplies nearby context.
  • Metric: Profile complete is visible with a meaningful value.
  • Another signal: Avatar set helps people judge what to do next.
  • Representative record: Personal details makes the example specific.
  • Second record: Team role 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 profile without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for preferences; clarify who can continue.
  • Success after choosing Save profile; 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

Profile → Preferences → Save profile → Review outcome

Patterns used

Form, Profile, Preferences, Notifications, 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 Personal details with Team role. Make profile complete clear, then use avatar set 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 “Save profile” action. The happy path alone is not enough.

Related UI examples: Role Permission Setup, Verification Center, SSO Setup.

Start from this in Figr

Design a profile setup screen for our existing software product. Use our real design-system tokens, components and product language. Show Profile and Preferences, include believable records such as Personal details, and make save profile easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr