Profile Switching

NHF explicitly flagged membership in up to five local chapters as a unique requirement, with the specific need to clarify affiliation and prevent double-reporting of activities. Profile switching solves this without forcing users to maintain separate accounts, which would multiply onboarding friction and fragment activity data. For Org Admins who surface as Coordinators on mobile, seamless context switching removes the need for separate login flows. At platform scale, this pattern lets Norse onboard users active across multiple partner organizations without account proliferation, directly supporting multi-tenant growth and reducing coordinator overhead for managing duplicated records.

The active role/organization context is held in a Riverpod state notifier that persists the selection to Drift local storage so it survives app restarts. On context switch the app invalidates all organization-scoped providers and re-fetches the module registry, home widgets, and navigation tabs for the new tenant from the REST API bootstrap endpoint. The Role Switch Widget is a bottom-sheet picker listing the user's available role-org pairs from user_organization_roles. Tenant scoping is enforced by injecting the active organization ID as a header in ApiHttpClient on every request, preventing cross-org data leakage. Users with a single role-org pair do not see the switch entry point. Flutter page transitions must maintain WCAG focus management during context change.