---
id: TST-PFM-NOT-072
title: hq notifications
kind: integration
product_area: platform
module: notifications
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js
implements:
  - ATS-PFM-NOT-001-11
  - ATS-PFM-NOT-003-07
  - ATS-PFM-NOT-012-02
  - ATS-PFM-NOT-012-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned records in the prepared integration workspaces; seeded workspace
  identities remain shared fixtures.
assertion_bindings:
  - scenario: ATS-PFM-NOT-001-11
    suite: TST-PFM-NOT-072
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#lists
        every application’s definitions, narrowed by application and status
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#answers
        each definition’s declaration without its templates or data schema
  - scenario: ATS-PFM-NOT-003-07
    suite: TST-PFM-NOT-072
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#leaves
        out an invited user, a portal user, a user of another customer and an id
        that is nobody’s
  - scenario: ATS-PFM-NOT-012-02
    suite: TST-PFM-NOT-072
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        refused without an active staff access grant, naming nothing of the
        tenant
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        answered with an active grant into the tenant, the same page its
        administrator reads
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        refused for another tenant, the grant reaching only the tenant it names
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        refused for a tenant that does not exist
  - scenario: ATS-PFM-NOT-012-04
    suite: TST-PFM-NOT-072
    assertions:
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        answered with an active grant into the tenant, the same page its
        administrator reads
      - >-
        services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js#is
        refused without an active staff access grant, naming nothing of the
        tenant
evidence:
  - >-
    services-platform:modules/notifications/tests/integration/services/centre/hq-notifications.integration.spec.js
  - The file and referenced assertion titles exist at the pinned commit.
dependency_evidence:
  - >-
    Real: PostgreSQL with row-level security on, the real staff access grant and
    its assignment, the real reads. Doubled: nothing.
  - 'Never doubled: the database, the grant reader or any read.'
---

# hq notifications

## Verification Boundary

This suite exercises the local services and prepared PostgreSQL database. API lifecycle cases use signed test contexts through the real route handler; they do not invoke the deployed gateway.

## What This Suite Proves

Its cases exercise restrict global catalog access to HQ; exclude ineligible and cross-customer users; require an active customer access grant; read HQ History only while access is granted.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

## What It Does Not Prove

Local outcomes do not prove deployed queues, external provider acceptance, production credentials or complete browser behavior. No fresh execution or conformance result is claimed.

## Real Dependencies and Test Doubles

The notification fixtures use real PostgreSQL and module logic. Queue publication, visibility changes, nudges and installed channel adapters are recorded at their seams when the suite needs them. Signed API contexts replace the authorizer key in API suites.

## Must Not Be Doubled

Database constraints, workspace policy, state guards and the service operation under test must remain real. Recording a provider or queue call must not replace the submission, claim or outcome logic being checked.