BC
Brad CodyAdministrator
Current productAccess and application shell
Reverse spec drafted

User account menu

Signed-in user identity, profile actions and session controls.

Observed route/adminFuture Spec 04
Current maturityVisible identity control; menu options unverified
Evidence confidencePartially verified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

The bottom of the Admin and Settings sidebar displays the signed-in identity and access label with a three-dot account action. During initial loading it shows Signed-in user / Loading access, then resolves to [email protected] / administrator. The menu itself was not opened during this pass.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Avatar or initialShows a single-letter initial after identity resolution.Verified live
Primary identifierTransitions from Signed-in user to [email protected].Verified live
Access labelTransitions from Loading access to administrator.Verified live
Three-dot actionExposes an Open account menu affordance.Trigger verified; menu not opened

User journeys

Current flows

01

Resolve signed-in identity

  1. Restore session
  2. Render loading identity
  3. Resolve User and Membership
  4. Render identifier and access label
Observed result

Verified in Admin and Settings shells.

02

Use account action

  1. Open account menu
  2. Choose profile, preferences, security, help, Workspace switch or sign out
Observed result

Expected menu structure; current options unverified.

State model

Current and expected states

Loading

Signed-in user / Loading access.

Resolved

[email protected] / administrator with B avatar.

Menu open

Not verified.

Session expired

Not verified.

Product rules

Non-negotiable boundaries

  • Global User Profile data is separate from Workspace Membership data.
  • The access label is descriptive and must not be the sole authorization check.
  • Sign out must always be available.
  • Sensitive security actions may require recent authentication.
Dependencies
Supabase sessionUser ProfileWorkspace MembershipRole label or access summaryProfile and security routes

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 04 owns closure →
  1. Menu contents and actions are unverified.
  2. Display currently falls back to the email instead of a completed personal name.
  3. Sign out, profile, notification preferences and security routes have not been validated.
  4. Session-expired behavior is unknown.

Future alignment

Required evolution

  • 01Include My Profile, notification preferences, connected accounts, Workspace switch, Security, Help and Sign out.
  • 02Display the user’s preferred name when available while retaining a clear account identifier.
  • 03Provide sign-out-all and other sensitive controls through protected Security flows.

Current baseline

Acceptance record

  • Loading and resolved user identity states are visible.
  • The account action is present.
  • Unverified menu options are not represented as implemented.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented