---
id: TST-PFM-CSH-005
title: Refused staff bookmark
kind: browser-lifecycle
product_area: platform
module: console-shell
revision: 1
status: draft
source_sha:
  rhythm-v2-docs: 25e253cb434aac6603ee294e3ca197ab6c4bfd0b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: react-console
files:
  - e2e/controlled/staff-deep-link.controlled.spec.ts
implements:
  - ATS-PFM-CSH-013-04
  - FAS-PFM-CSH-03-04
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 15
isolation: >-
  Fresh browser context with existing development test accounts; licensing cases
  clean up only their own named overrides.
evidence:
  - >-
    react-console:e2e/controlled/staff-deep-link.controlled.spec.ts at
    baf6dae382d6f41dce976c7f848667ccc37e076f
  - >-
    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
  - >-
    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
binding_boundary:
  - scenario: ATS-PFM-CSH-013-04
    provenance: test
    source: >-
      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
    note: >-
      This file supplies the complete stated scenario outcome at its declared
      test boundary.
  - scenario: FAS-PFM-CSH-03-04
    provenance: test
    source: >-
      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
    note: >-
      This file supplies the complete stated scenario outcome at its declared
      test boundary.
---

# Refused staff bookmark

## Verification Boundary

The browser signs in through a staff bookmark while one strict context response is replaced with a clearance refusal. Assertions check HQ, the explanatory notice and absent emergency and staff-access panels.

This register records static review at the supplied source commits. The suite exists, but this pass does not run it or mark its conformance verified.

## What This Suite Proves

- Refused staff entry returns to HQ without emergency access.
- A refused staff bookmark returns to an explained HQ context.

Bindings that span files are collective: each file contributes only its recorded assertions. The exact anchors are in frontmatter.

## What It Does Not Prove

The register claims only the linked scenario outcomes at this boundary. It establishes no passing deployment result, complete permission matrix or unlisted cross-capability journey. Proposed scenarios and the remaining lifecycle, invariant and race obligations stay in the coverage findings.

## Real Dependencies and Test Doubles

The browser, sign-in session and unmodified development reads are real. The named context response is fulfilled by the test with a deterministic refusal; that interception is part of this controlled boundary.

## Must Not Be Doubled

Do not replace the console’s routing, menu assembly, provider, destination guards or measured DOM with canned component outcomes. Demonstration responses or the declared controlled refusal are doubles at the response boundary, not substitutes for the console behavior under examination.