Profile setup

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?