Your account
HOL-D092Story implementation: In progress

Choose and switch my workspace

account · Proposed launch phase 1

Start from Home

Review as Registered user

User story

As a registered member, I want to switch between my Member, Professional and organization workspaces so I can use the right tools with one account.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Resolve landing from safe original intent and explicit eligible selection, otherwise an actual saved still-eligible preference; with no selected preference open magazine Visitor Home. Member/Professional/named organization remain independent workspaces. Default member values are not user choices; first visit must not force a private Home or blocking workspace chooser.
  • Use Member for both free registered and paid members; actual features follow the independent membership entitlement.
  • Offer one Member workspace, one combined Professional workspace for all selected professional identities, and each managed organization by name.
  • Offer a visible, non-blocking workspace choice and remember an actual selection for that account. With no selected preference, use magazine Visitor Home. Preserve a still-valid choice as more contexts are added.
  • Honor a safe authorized same-account original destination and explicit current selection; otherwise restore an actual saved eligible preference. With no selected preference, use magazine Visitor Home and preserve the signed-in identity.
  • Identify the active workspace and organization prominently. A remembered context is a preference, never permission; removed management access disappears and direct entry is denied.
  • Preserve the same account, personal data and reader entitlement. Internal HOL roles retain assigned workspaces and required MFA; new public signup never grants them.
  • Opening/editing personal Profile & settings from Member, Professional, org or staff must preserve the actual selected Home. Only explicit eligible Home/workspace selection writes that preference; no-choice public Home and safe original return retain their existing priority.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on the free Member Home. For a local example use Sign in → Try a demo account → Alex Morgan → Open account, then choose Member in the account/workspace menu if a remembered workspace opens. This is a genuine local account; no paid access is supplied.

Navigation from sign-in

  1. 01Open the fictional Registered user account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin on the account’s signed-in Home. Open the account/workspace menu and choose Member, Professional or an authorized named organization. The feature starts at that menu; an account with no selected preference begins on magazine Visitor Home and can choose its workspace from the menu.

Feature checks start here

Choose and switch my workspace

October19 scoped dummy-account fixes are available in dev. Named Home/reload and truthful profile checks pass; exact no-preference Professional browser coverage awaits a suitable account. Full-story acceptance remains separate. Connected in dev; full acceptance remains In progress. Member, one Professional workspace and named organizations use the same account. Selection survives reload; transferred-away organization access disappears while personal access remains. Remaining arrival/stale-selection cases stay open.

  1. 03Test Creator/Guide/Athlete explicit Professional, explicit Member and named-org selections; remembered valid selection; no preference; stale/revoked preference; Home/reload; and same-account joining return. Public Home may be shown to a signed-in person without signing them out or switching their role.
  2. 04From this account’s Home open the account/workspace menu. Select Member, Professional and each currently authorized named organization available to this same identity; confirm the visible name and role/context on each destination.
  3. 05Choose Home and reload in each selected context. Return to the account and confirm its last valid workspace is remembered, with the same account identity and free/paid access state.
  4. 06When entering a particular dummy role, arrive at the requested permitted Home without inheriting another account’s old membership/signup continuation. Keep legitimate same-account return behavior intact.
  5. 07For dedicated staff dummy accounts, review the assigned Home without password or MFA prompts, then sign out to Visitor. Real staff accounts and protected operations retain normal MFA. Building tools or content inside these Homes is outside this immediate auth-entry check.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Resolve landing from safe original intent and explicit eligible selection, otherwise an actual saved still-eligible preference; with no selected preference open magazine Visitor Home. Member/Professional/named organization remain independent workspaces. Default member values are not user choices; first visit must not force a private Home or blocking workspace chooser.
  • Represent contexts as Member, Professional or a specific organization ID; resolve the current eligible set from account/person labels and accepted org assignments. Store only the preference, with safe return-destination validation.
  • Use one trusted account ID; keep email verification, professional labels, reader entitlement, organization-scoped access and internal HOL staff assignments independent.
  • Validate actor, organization/person IDs, current access and expected revision at the trusted boundary. Remembered workspace, URL, fixture choice and client flags never grant permissions.
  • Persist only the records needed for this outcome, including owner-scoped drafts and decision/assignment/consent audit where applicable. Keep private evidence and contacts out of public projections.
  • Enforce the selected requirements above in database/API policies, with idempotent transitions, concurrent-update handling and denied cross-account writes.
  • Use isolated local synthetic data only; no hosted migration, public service connection, real credentials/recipients, live payment or deployment.
  • Store account-scoped workspace preference and derive eligible contexts from current trusted professional and organization records. Revalidate after revocation and never persist a stale authorization grant.

How to verify in dev

  1. Test Creator/Guide/Athlete explicit Professional, explicit Member and named-org selections; remembered valid selection; no preference; stale/revoked preference; Home/reload; and same-account joining return. Public Home may be shown to a signed-in person without signing them out or switching their role.
  2. Restore the last valid context across sessions, revoke an organization manager assignment and replay its saved URL/preference; deny org data and safely return to an eligible context without changing membership.
  3. Test owner, manager, unrelated account, unverified account and permitted HOL staff where relevant; deny self-grants and cross-organization access.
  4. Exercise success, interrupted/repeated requests, expiry/revocation and stale/concurrent updates; verify stable identity, correct public visibility and preserved unrelated account data.

Before this can work

  • Begin on the free Member Home. For a local example use Sign in → Try a demo account → Alex Morgan → Open account, then choose Member in the account/workspace menu if a remembered workspace opens. This is a genuine local account; no paid access is supplied.
  • Use a fictional registered member account and begin at its Home with its actual permitted context.
  • Use actual local provider sessions and persisted state; record connected UI and direct permission checks separately.

Connected stories