---
id: TST-PFM-SEC-221
title: HQ workspace shortcuts request checks
kind: api-lifecycle
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js
implements:
  - ATS-PFM-SEC-002-12
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#the HQ home page’s
      tenant shortcuts (end to end)
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#pinning a tenant
      and reading the home page
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers 200 to the
      pin
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers the
      shortcut with the tenant the path named
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers the
      instant it was pinned and no instant it was opened
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers the name
      of the customer that owns it beside the tenant
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#puts it in the
      pinned list of the home page
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#leaves the recent
      list without it, because pinning is not opening
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers 200 to the
      same pin again, changing nothing
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#recording that a
      tenant was opened, and unpinning it
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers 200 to the
      open
  - provenance: test
    source: 'services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#counts each open'
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers 200 to the
      unpin, with the caller’s shortcuts as they now stand
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#takes the tenant
      out of the pinned list
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#keeps it among the
      recent ones, because the person opened it
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers 200 to the
      same unpin again
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#one staff member’s
      shortcuts are never another’s
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#answers the
      support representative their own pinned tenant (the premise both rows exist)
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#never answers the
      administrator the tenant the other person pinned
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#never answers the
      support representative the tenant the administrator pinned
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#leaves the other
      person’s list untouched when one of them unpins
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#a caller who is
      not Rhythm staff
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses an
      administrator of a customer reading the home page as 403, because these are system routes
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses that
      administrator pinning a tenant as 403
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses that
      administrator recording an open as 403
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses an
      anonymous call as 401
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#leaves the
      administrator’s own lists with nothing of that tenant after those refusals
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#a tenant that does
      not exist
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses a pin of
      it as 404
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses an unpin
      of it as 404
  - provenance: test
    source: >-
      services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js#refuses recording
      that it was opened as 404
dependency_evidence: >-
  The local request harness exercises the route dispatcher and the prepared database. The suite
  controls the signing key at the declared seams; those collaborators remain outside its live proof.
evidence:
  - 'services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js'
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: 'services-platform:modules/tenants/tests/e2e/hq-tenant-shortcuts.e2e.spec.js'
  explicit_no_doubles: false
  identified_double_boundaries:
    - the signing key
---
# HQ workspace shortcuts request checks

## Verification Boundary

The file exercises public request handling through the local service harness. The assertion references identify the source checks for HQ workspace shortcuts.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The local request harness exercises the route dispatcher and the prepared database. The suite controls the signing key at the declared seams; those collaborators remain outside its live proof.

## Must Not Be Doubled

Keep route dispatch, signed-context verification and the exercised service decisions real. A test key can supply signatures, but replacing the authorization decision cannot prove request enforcement.