UX Patterns Guide
UI + UX Task And Workflow Patterns established

Profile setup

Provide a guided profile setup surface that shows the current profile, distinguishes required, recommended, optional, private, public, and managed fields, previews visibility, saves partial progress, and lets users return later without blocking unrelated work.

Open in lab Compare alternatives
Decision first

Choose this pattern when the problem matches

Use when

  • Users already have an account or profile and need guided help to complete, review, enrich, or update it.
  • Profile quality affects collaboration, discovery, scheduling, trust, public presentation, marketplace identity, or directory usefulness.
  • The product can distinguish required access fields from optional enrichment and can enforce visibility choices downstream.

Avoid when

  • The user is creating their first profile identity rather than completing an existing profile.
  • The task is account creation, authentication, password setup, onboarding, notification preferences, or general account settings.
  • The product cannot explain where profile data appears or honor visibility choices.
  • Profile completion is mainly a growth tactic unrelated to the user's current task.
  • The team cannot support partial saves, managed-field correction, skipped optional fields, or later editing.

Problem it prevents

After an account or initial profile exists, products often pressure users to fill every profile field, but unclear visibility, managed-field conflicts, and mandatory optional details can expose personal data or delay the user's real task.

Pattern anatomy

What a strong implementation has to make clear

User need

The user already has an account, workspace membership, community profile, employee directory entry, developer profile, marketplace identity, or collaboration profile.

Pattern promise

Provide a guided profile setup surface that shows the current profile, distinguishes required, recommended, optional, private, public, and managed fields, previews visibility, saves partial progress, and lets users return later without blocking unrelated work.

Required state

Current profile preview with existing values

Recovery path

Users disclose unnecessary personal information to satisfy a completion prompt.

Access contract

Use explicit field labels and required or optional text for every profile value.

Quality bar

The difference between expert and weak execution

Strong implementation

Specific, visible, recoverable

  • A workspace profile setup checklist shows that display name is complete, photo is optional with initials fallback, title is managed by HR, time zone helps scheduling, and location visibility is set to Team only.
  • A developer profile readiness page previews the public profile, recommends a bio and pinned project, warns that public fields are searchable, and lets the user save partial progress.
  • A user adds time zone and pronouns, leaves photo and social links blank, sees the team-card preview update, and returns to the project they were working on.
  • A user tries to edit a synced job title, sees who manages it, saves other profile changes, and gets a route to request the title correction.
Weak implementation

Vague, hidden, hard to recover from

  • A complete your profile banner blocks the product until the user uploads a photo, birthday, phone number, location, and social links.
  • A profile setup page asks for department and job title even though those fields are later overwritten by identity-provider sync.
  • A user provides a personal phone number to dismiss a profile-completion warning, then discovers it is visible to external collaborators.
  • A user abandons because profile setup is mixed with account security, onboarding tips, notification preferences, and marketing consent.
UI guidance
  • Render profile setup as a focused completion surface for an existing account or profile, with current profile preview, missing recommended fields, managed-field notices, visibility controls, skip or do-later paths, and clear save state.
  • Keep profile setup separate from account creation, first-run onboarding, generic settings, and initial profile creation: it helps users improve an already established profile without treating every optional profile detail as mandatory.
UX guidance
  • Use profile setup when a user already has a usable account or profile and needs guided help to make the profile complete enough for collaboration, public identity, trust, or discovery.
  • Explain why each missing field matters, where it will appear, which fields are optional, which are managed by an organization, and what the user can safely skip or finish later.
Implementation contract

What the implementation must handle

States

  • Current profile preview with existing values
  • Missing required field state
  • Recommended but skippable field state
  • Optional field intentionally blank state

Interaction

  • Opening profile setup loads the current saved profile and clearly distinguishes already-complete, missing, recommended, optional, managed, and visibility-sensitive fields.
  • Saving updates only the edited profile values and preserves skipped recommended or optional fields as intentional choices rather than validation failures.
  • Visibility changes update the preview or audience labels before save and are persisted with the relevant field.
  • Managed or synced fields remain read-only or clearly constrained, with source and correction route visible before users try to edit them.

Accessibility

  • Use explicit field labels and required or optional text for every profile value.
  • Do not communicate completeness, public/private state, or managed status with color alone.
  • Expose profile preview updates with a status region only when the change matters; do not move focus after every keystroke.
  • Keep skip, save, request-change, visibility, and return actions keyboard reachable.

Review

  • Which profile fields are truly required, and which are only recommended?
  • Where will each field appear after save?
  • Which fields can be seen by public visitors, external collaborators, team members, apps, or only the user?
  • Can users skip optional fields and still complete their real task?
Interactive lab

Inspect the states before you copy the pattern

Complete an existing profile without forcing disclosure

Review current profile readiness, fill required and recommended fields, skip optional details, inspect visibility and managed fields, save partial progress, return to the source task, and compare completion-meter, public-default, synced-field, no-skip, mixed-settings, and repeated-nag failures.

Profile setup
Interactive demo is ready

Launch the live UI/UX lab when you want to inspect states, keyboard behavior, and common failure modes.

State To Inspect

Current profile preview with existing values

Keyboard / Access

Initial focus lands on the profile setup heading or first missing required field after a short context message.

Avoid Generating

Calling every optional field required profile completion.
Evidence trail

Source-backed claims behind this guidance

Atlassian profile and visibility settings

Atlassian Support - checked

Atlassian supports profile visibility controls, profile photo fallback, public-name behavior, and warnings about profile information surfaces.

Slack customize member profiles

Slack Help Center - checked

Slack supports collaboration profile fields, searchable fields, admin-managed fields, and identity-provider syncing.

GitHub about your profile

GitHub Docs - checked

GitHub supports user control over public profile information, profile README, pinned items, status, and visibility options.

Slack change your display name

Slack Help Center - checked

Slack supports full-name and display-name distinctions, mention behavior, non-English names, and SSO-managed restrictions.

NN/g Marking Required Fields in Forms

Nielsen Norman Group - checked

NN/g supports clearly communicating required and optional fields, relevant to profile setup with required versus recommended details.

Full agent/debug reference

Problem Context

  • The user already has an account, workspace membership, community profile, employee directory entry, developer profile, marketplace identity, or collaboration profile.
  • The profile can be improved with optional fields such as photo, bio, pronouns, title, department, time zone, location, social links, skills, languages, or pinned work.
  • Some fields may affect recognition, scheduling, trust, discovery, search, assignments, comments, public pages, or third-party app access.
  • Some values may be synced from an identity provider, administrator-managed, or visible to different audiences.
  • The user may have arrived from an in-product prompt and needs to return to the original task after setup.

Selection Rules

  • Choose profile setup when an existing profile is usable but incomplete, stale, or missing recommended details that improve collaboration, discovery, trust, or public presentation.
  • Use create user profile when the user is first defining the visible identity required to establish a profile.
  • Use account creation when the main task is credentials, verification, persistence, recovery, or authorization.
  • Use onboarding when the user needs first-use product orientation or activation rather than profile-field readiness.
  • Use inline edit when the user is changing one visible profile value in place rather than working through a guided profile setup surface.
  • Use review before submit when profile changes need a final commit gate because they are public, high-risk, regulated, or hard to undo.
  • Do not block unrelated product use for optional profile fields unless a field is legally, safety, or access-policy required.
  • Show where each requested profile value appears before asking for it, especially for public, external, searchable, or app-visible fields.
  • Let users save partial progress and return to the originating task when profile setup is prompted from inside another workflow.

Required States

  • Current profile preview with existing values
  • Missing required field state
  • Recommended but skippable field state
  • Optional field intentionally blank state
  • Field visibility or audience state
  • Managed or synced field state
  • Partial save and return later state
  • Failed save with preserved draft state

Interaction Contract

  • Opening profile setup loads the current saved profile and clearly distinguishes already-complete, missing, recommended, optional, managed, and visibility-sensitive fields.
  • Saving updates only the edited profile values and preserves skipped recommended or optional fields as intentional choices rather than validation failures.
  • Visibility changes update the preview or audience labels before save and are persisted with the relevant field.
  • Managed or synced fields remain read-only or clearly constrained, with source and correction route visible before users try to edit them.
  • Skipping profile setup returns the user to the originating workflow without discarding existing profile data or repeatedly blocking unrelated tasks.
  • Failed saves preserve typed drafts, uploaded-photo state where possible, visibility choices, and the user's return path.
  • Public or external profile changes are not presented as final until the backend confirms the saved profile state.

Implementation Checklist

  • Inventory all profile fields and label each as required, recommended, optional, managed, synced, public, organization-visible, team-visible, private, or app-visible.
  • Define the minimum profile needed for access separately from recommended profile completeness.
  • Show a current profile preview for the most important destination such as team card, directory row, public profile, comment byline, or marketplace listing.
  • Keep account security, notification settings, marketing consent, billing, and product onboarding outside the profile setup flow unless directly related to profile visibility.
  • Persist partial progress and record skipped recommended fields without nagging users on every unrelated page.
  • Provide a managed-field explanation and request-change route for identity-provider or administrator-owned values.
  • Test long names, no photo, initials fallback, hidden location, public bio, managed title, skipped recommended fields, failed save, mobile layout, screen readers, keyboard navigation, and high zoom.

Common Generated-UI Mistakes

  • Calling every optional field required profile completion.
  • Blocking the main product until users add photos, biographies, birthdays, phone numbers, or social links.
  • Publishing setup fields without visibility labels or preview.
  • Letting users edit synced fields that will be overwritten later.
  • Mixing profile setup with onboarding, security setup, notification preferences, marketing consent, or billing.
  • Using a percentage-complete meter that pressures users to reveal unnecessary personal information.
  • Repeating profile completion prompts after users intentionally skipped optional fields.
  • Failing to return users to the task that launched profile setup.

Critique Questions

  • Which profile fields are truly required, and which are only recommended?
  • Where will each field appear after save?
  • Which fields can be seen by public visitors, external collaborators, team members, apps, or only the user?
  • Can users skip optional fields and still complete their real task?
  • Which fields are synced or admin-managed, and how can users correct them?
  • Does the setup surface preserve partial progress and return to the originating workflow?
Accessibility
  • Use explicit field labels and required or optional text for every profile value.
  • Do not communicate completeness, public/private state, or managed status with color alone.
  • Expose profile preview updates with a status region only when the change matters; do not move focus after every keystroke.
  • Keep skip, save, request-change, visibility, and return actions keyboard reachable.
  • Associate managed-field explanations and visibility labels with the relevant inputs.
  • Ensure profile photos have meaningful alt text or initials fallback and that upload is not required to continue.
  • Make partial-save and failed-save states available to screen readers while preserving entered values.
Keyboard Behavior
  • Initial focus lands on the profile setup heading or first missing required field after a short context message.
  • Tab order follows profile preview summary, required fields, recommended fields, optional fields, visibility controls, managed-field routes, save, skip, and return actions.
  • Changing visibility does not move focus unexpectedly.
  • Submit with missing required profile data moves focus to the specific error or error summary.
  • Save preserves optional skipped fields and leaves focus on a saved status or return action.
  • Cancel or return restores focus to the surface that launched profile setup when possible.
Variants
  • Profile completion checklist
  • Member profile setup
  • Public profile setup
  • Directory profile setup
  • Developer profile setup
  • Marketplace seller profile setup
  • Collaboration profile readiness
  • Managed employee profile
  • Profile visibility setup
  • Profile enrichment prompt

Verification

Last verified: