The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/crm/contacts/{contactId} | Follows a contact link containing query information while signed out. | CAP-PFM-CSH-009 | The sign-in experience begins. | documented react-console:docs/url-architecture.md#6. Tenant from the URL |
| 2 | getMySecurityContext | Signs in and waits for access to the workspace requested by the link. | CAP-PFM-CSH-010 | The URL-entry request names the requested workspace explicitly. | observed react-console:lib/security-context/provider.tsx:openTenantId |
| 3 | /console/{tenantId}/crm/contacts/{contactId} | Completes entry to the requested contact. | CAP-PFM-CSH-009 | The intended workspace, contact and query information remain the destination. | documented react-console:docs/url-architecture.md#6. Tenant from the URL |
| 4 | /console/{tenantId}/crm/contacts/{contactId} | Reloads the record page. | CAP-PFM-CSH-009 | The same workspace record remains open. | test react-console:e2e/mock/url-architecture.mock.spec.ts#a record deep link survives a reload |
| 5 | /console/{tenantId}/crm/contacts | Opens the contacts list and then uses browser history. | CAP-PFM-CSH-009 | History restores the earlier contact and list destinations. | documented |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 1 | The colleague sent a link using the earlier address scheme. | Compatibility handling places it in the remembered workspace. | The record identifier and query information survive the redirect. | test react-console:e2e/mock/url-architecture.mock.spec.ts#an old tenant-less URL lands on its canonical URL, id and query kept |
| alternate | 2 | A cleared Rhythm staff member follows the workspace link. | The staff session enters the requested workspace directly. | The requested contact becomes the working destination. | documented react-console:docs/url-architecture.md#11. Decisions made during the build |
| failure | 2 | The link names an unknown workspace. | The workspace entry response presents not found. | The requested workspace page remains unopened. | test react-console:e2e/mock/url-architecture.mock.spec.ts#an id no tenant has shows not found |
| failure | 2 | The person cannot reach the named workspace. | The console explains the refusal and offers a reachable return context. | The requested workspace is not entered. | observed react-console:components/console/tenant-id-gate.tsx:TenantIdGate, deniedReturnTenant |
| failure | 2 | The staff member has no clearance for the requested workspace. | Rhythm HQ opens with an explanatory notice. | The console does not start an emergency-access dialog. | test react-console:e2e/controlled/staff-deep-link.controlled.spec.ts#an uncleared staff member's deep link goes to Rhythm HQ with a notice, not the emergency-access dialog |
| failure | 3 | The linked work is in an application unavailable to the organization. | The page body explains product unavailability. | Home and application-list destinations provide ways onward. | test react-console:e2e/mock/application-access.mock.spec.ts#a deep link into one of them says the application isn't available |
| Id | Statement | Provenance |
|---|---|---|
01 | Sign-in can restore the page and query requested by a direct link. | test react-console:e2e/dev/url-architecture.dev.spec.ts#a signed-out deep link goes through sign-in and comes back to the same page and query |
02 | Reload preserves the workspace record destination. | test react-console:e2e/mock/url-architecture.mock.spec.ts#a record deep link survives a reload |
03 | An unknown workspace identity produces a not-found response. | test react-console:e2e/mock/url-architecture.mock.spec.ts#an id no tenant has shows not found |
04 | Compatibility handling retains the old link’s record identity and query. | test react-console:e2e/mock/url-architecture.mock.spec.ts#an old tenant-less URL lands on its canonical URL, id and query kept |
End-to-end policy: required: Sign-in return, workspace entry and browser history require browser evidence. Current bindings cover specific destinations; a contact-specific sign-in and history journey still needs direct proof.