Skip to content

JNY-PFM-SEC-005Approve and end customer workspace access for support

Markdown

JNY-PFM-SEC-005

Approve and end customer workspace access for support

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

KindJourneyProduct areaPlatformModuleSecurity, Customers and WorkspacesRevision1End-to-endRequired

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

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

Goal
Obtain customer-approved access for a support task, use the workspace and revoke the grant when the task is complete.
Screens
/hq/tenants/{tenantId}/console/{tenantId}/security/rhythmAccess/console/{tenantId}

Steps

#SurfaceActionCapabilityExpectedProvenance
1requestHqTenantAccessRequest two days of Read Only from HQ with the support reason.CAP-PFM-SEC-017The backend stores a waiting request without granting access and returns its notification outcome.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#takes the request, 200, answering it waiting for a decision with the names of what it would reach
2/console/{tenantId}/security/rhythmAccessApprove the request as an authorized customer security administrator.CAP-PFM-SEC-017The backend activates the grant for the approved duration within the request limit.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#approves it, 200, for the days the administrator chose
3/console/{tenantId}Enter the workspace through HQ.CAP-PFM-SEC-007The mock console displays the staff-access banner on workspace entry.test
react-console:e2e/mock/hq-lists.mock.spec.ts#End Access ends the grant and returns to HQ; the tenant then asks for access again
4revokeTenantStaffAccessRevoke the grant as the customer administrator.CAP-PFM-SEC-017The backend revokes it and fresh context evaluation no longer reports reach; existing cached authority can persist.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#takes the access away again when the administrator revokes it

Alternate and Failure Paths

PathFrom stepConditionPath takenOutcomeProvenance
alternate1An incident requires the emergency path.Open a valid emergency grant with Rhythm Administrator authority.The backend returns the opened grant and notification outcome.test
services-platform:modules/security/tests/e2e/staff-access.e2e.spec.js#opens the grant, 200, answering it with the names of what it reaches and the notice’s outcome
alternate3The staff member already holds standing access.Enter through that standing grant.The mock entry uses no emergency dialog and shows a banner without an expiry.test
react-console:e2e/mock/hq-lists.mock.spec.ts#a standing grant (no expiry) enters with no dialog, and the banner names no end
failure2A Power User attempts to decide the request.Reject the decision for missing staff-access authority.The request remains waiting.test
services-platform:modules/security/tests/e2e/power-user-staff-access.e2e.spec.js#leaves the request waiting after the Power User’s refused decisions
failure3Staff attempt entry before any access is granted.The mock console offers the emergency-access dialog.That mock establishes dialog behavior, while staff-role authorization is established by backend emergency tests.test
react-console:e2e/mock/hq-lists.mock.spec.ts#without a grant asks for emergency access, validates it, then switches in with only the tenant's navigation

Assertions

IdStatementProvenance
01A waiting request does not appear as reachable workspace access in fresh evaluation.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#grants the staff member nothing while the request is waiting
02Approval introduces the grant into fresh reachable-access evaluation.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#is what lets the staff member into the tenant, and only then
03Customer revocation removes that reach from a fresh context; it does not prove immediate gateway-cache eviction.test
services-platform:modules/security/tests/e2e/approved-access.e2e.spec.js#takes the access away again when the administrator revokes it

End-to-end policy: required: The intended journey connects a staff operator in HQ with an administrator in the customer’s Security area. Backend grants and mock banners provide separate evidence; a real browser journey must establish their combined behavior.

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.