---
id: ADR-PFM-CSH-010
title: HQ and Workspace Navigation Use Separate Modes
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Present HQ and workspace work in separate modes, preserving a reachable
  remembered workspace for compatibility links while bare-root staff landing
  selects HQ.
constrains:
  - DOM-PFM-CSH-001
  - WF-PFM-CSH-001
  - WF-PFM-CSH-004
  - SCR-PFM-CSH-003
  - SCR-PFM-CSH-007
origin: >-
  react-console:docs/url-architecture.md#11. Decisions made during the build,
  item 24 (Andrew, 2026-10-15; final acceptance 2026-10-15)
alternatives:
  - option: Combine Rhythm HQ and workspace navigation for staff
    why_not: Combined navigation obscures the authority and organization in use.
  - option: Resume the remembered workspace for staff on every landing
    why_not: >-
      Remembered customer selection is inappropriate for a staff landing without
      an explicit workspace destination.
consequences:
  - Header and menus follow one shared presentation mode.
  - >-
    Leaving clears local workspace selection before the follow-up context
    answer.
  - >-
    Denied staff links navigate to HQ, where emergency access is a separate
    task.
supersedes: []
evidence:
  - >-
    react-console at baf6dae: components/console/use-shell-mode.ts;
    lib/security-context/{boot.ts,provider.tsx};
    e2e/mock/staff-landing.mock.spec.ts
---
# HQ and Workspace Navigation Use Separate Modes

## Context

Staff perform Rhythm administration and customer work under different authority. The interface needs to identify which context is in use.

## Decision

Present HQ and workspace navigation separately. Bare-root staff landing selects HQ, while workspace deep links use strict entry. Keep a reachable remembered workspace for older links.

## Alternatives Considered

A combined map obscures working context. Automatic remembered-workspace landing would place staff in customer work without an explicit destination.

## Consequences

Menu and header follow the same mode. Refused staff links lead to HQ with notice. Leaving removes the selected workspace before the follow-up context response.