Rhythm 2.0 Specifications

Appearance

WF-PFM-SEC-011Grant and end staff entry to a customer workspace

Markdown

WF-PFM-SEC-011

Grant and end staff entry to a customer workspace

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-SEC-017, CAP-PFM-SEC-001

KindWorkflowProduct areaPlatformModuleSecurity, Customers and WorkspacesRevision1ExaminercodexExamined on2026-10-23

Read atservices-platform ad3f6a65react-console baf6dae3

Grant and end staff entry to a customer workspace ​

What It Does ​

Staff customer entry uses ordinary scoped assignments backed by recorded grants. HQ system routes retain their separate staff-administration authority; they are not a substitute grant for ordinary customer work.

The Flow ​

The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.

When Something Fails ​

Customer decisions, emergency entry and standing reconciliation have different actors and notice paths. The customer can revoke standing access, and deployment preserves that choice. Notification failure and cached authority remain separate from committed grant state.

Sequential duplicate request checks return the held request or grant; emergency entry can reuse standing access. Active grants have target uniqueness, while concurrent requested-row exclusion remains unknown. Standing reconciliation preserves manually revoked grants.

Grant decisions, matching assignments and history transact together under active-grant uniqueness. Requested-row creation uses a check-before-insert path without proved concurrent exclusion. Assignment validity governs fresh evaluation and grant expiry settles lazily; external notices and flushing follow commit.

Open Design Questions ​

The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.

Controls

50 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 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

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software