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.