---
id: TST-PFM-OPS-050
title: Hq licensing
kind: browser-lifecycle
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/dev/hq-licensing.dev.spec.ts
implements:
  - FAS-PFM-OPS-03-02
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: Fixture accounts and records identified by the suite’s run; cleanup follows the existing suite.
evidence:
  - >-
    react-console:e2e/dev/hq-licensing.dev.spec.ts at baf6dae382d6f41dce976c7f848667ccc37e076f: existing
    suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    react-console:e2e/dev/hq-licensing.dev.spec.ts#clicking a tenant in Rhythm HQ opens it in HQ; the
    Enter Tenant icon is what enters it
  - >-
    react-console:e2e/dev/hq-licensing.dev.spec.ts#the panel lists the Fictional Association's
    applications, names every author and folds the past overrides away
  - >-
    react-console:e2e/dev/hq-licensing.dev.spec.ts#the licensing panel withholds an application on the
    development tenant with a reason, and revokes it
  - >-
    react-console:e2e/dev/hq-licensing.dev.spec.ts#the tenant's own administrator reads Configuration ›
    Applications with the same words
---

# Hq licensing

## Verification Boundary

This suite exercises application licensing through the console browser flow. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks read real staff licensing, resolve visible authors, fold historical exceptions and follow a run-owned withhold through revocation. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

A deployed browser flow does not exhaust object invariants, race conditions or every permission combination. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The browser, console and deployed services are real. Fixture accounts and run-owned records supply the test data; deployment and fixture readiness remain external requirements.

## Must Not Be Doubled

The console interaction and displayed result under assertion remain real.