Continue in another workspace without reusing a record

Purpose

The switcher moves staff to corresponding work in another workspace without carrying a record reference across.

How It Works

The person opens the workspace switcher from the header. They review the current context and choose another reachable workspace. Navigation constructs a corresponding destination without the previous record. The workspace gate then establishes access to that destination. A confirmation currently precedes that result and can describe a switch that later fails. The product should align confirmation with successful entry and test cache replacement under delayed responses.

Relationships

Workspace entry supplies the destination context and refusal handling.
Address matching selects the retained list path.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Workspace choices come from the current reach list.The destination list belongs to the newly entered workspace.
Surfaces: console
Intent sources: react-console:docs/url-architecture.md#6. Tenant from the URL (decided by Andrew 2026-10-14; final acceptance 2026-10-15)

Controls

24 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-003 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.security-self.read`	api	tenant

Business Rules

8 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	The switcher uses only the reachable workspaces listed by the security context. origin: react-console:docs/url-architecture.md#6. Tenant from the URL (decided by Andrew 2026-10-14; final acceptance 2026-10-15) proved by `ATS-PFM-CSH-011-03`, `ATS-PFM-CSH-011-05`	permission	console	observed react-console:components/console/tenant-switcher.tsx:TenantSwitcher
`02`must prove Proposed	A workspace switch keeps the corresponding area and list, strips record identities and queries, and retains a planned page’s path. origin: react-console:docs/url-architecture.md#6. Tenant from the URL (decided by Andrew 2026-10-14; final acceptance 2026-10-15) proved by `ATS-PFM-CSH-011-01`, `ATS-PFM-CSH-011-02`, `ATS-PFM-CSH-011-06`, `TST-PFM-CSH-014`, `TST-PFM-CSH-029`	calculation	console	test react-console:lib/routes/__tests__/routes.test.ts#keeps the workspace and resource list and drops record ids and queries
`03`must prove Proposed	Choosing the already selected workspace initiates no navigation. proved by `ATS-PFM-CSH-011-04`	validation	console	observed react-console:components/console/tenant-switcher.tsx:TenantSwitcher
`04` Proposed	The switcher presents the current workspace and customer with copy controls for their identifiers.	policy	console	observed react-console:components/console/tenant-switcher.tsx:DetailRow
`05`must prove Proposed	Alternative workspace choices appear when more than one is reachable, and name-or-identifier search appears above six choices with an empty-result message. proved by `ATS-PFM-CSH-011-05`	calculation	console	observed react-console:components/console/tenant-switcher.tsx:TenantSwitcher
`06` Proposed	Entry in progress disables choices and shows progress, but the switcher reports the chosen workspace immediately before its entry is confirmed.	lifecycle	console	observed react-console:components/console/tenant-switcher.tsx:TenantSwitcher
`07`must prove Proposed	URL entry reads the destination context, clears cached data after a successful answer but before installing it, remounts workspace stores and keeps destination content gated while pending. proved by `ATS-PFM-CSH-010-09`, `ATS-PFM-CSH-011-02`	invariant	console	observed react-console:lib/security-context/provider.tsx:openTenantId; components/console/tenant-id-gate.tsx:TenantIdGate
`08`must prove Proposed	Successful workspace entry is remembered per person for customer landing and legacy links, while bare-address staff landing still targets HQ. no proof recorded yet	lifecycle	console	observed react-console:lib/security-context/provider.tsx:openTenantId; lib/auth/session.ts:rememberTenantFor

Scenarios

Id	Given	When	Then	Provenance
`01`	The person is viewing a contact in the first workspace.	They choose another workspace.	Navigation targets the contacts list in the chosen workspace without the contact identifier.	test react-console:e2e/mock/url-architecture.mock.spec.ts#switching tenant opens the same list under the other tenant's id, record ids dropped
`02`	The chosen destination cannot be reached anymore.	Its gate refuses entry.	The person receives a refusal with a route back to a reachable workspace.	observed react-console:components/console/tenant-id-gate.tsx:TenantIdGate, deniedReturnTenant

Planning

Implementation

Continue in another workspace without reusing a record ​

Purpose ​

How It Works ​

Relationships ​