---
id: TST-PFM-OPS-053
title: Application access
kind: browser-lifecycle
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/mock/application-access.mock.spec.ts
implements:
  - ATS-PFM-OPS-013-05
environment: mock
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: A browser context and controlled fixture responses.
evidence:
  - >-
    react-console:e2e/mock/application-access.mock.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/mock/application-access.mock.spec.ts#an application the organization does not have
    is absent from the sidebar
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#a deep link into one of them says the
    application isn't available
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#the same deep link opens for somebody whose
    organization has the application
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#the Applications page says which applications
    there are and why one cannot be used
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#brings the launcher up to date instead of
    leaving it offering what is gone
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#the policy editor offers an application's
    access key and saves a deny rule naming it
  - >-
    react-console:e2e/mock/application-access.mock.spec.ts#grants an override with a reason, then revokes
    it
  - 'react-console:e2e/mock/application-access.mock.spec.ts#asks for a reason long enough to be one'
---

# Application access

## 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 exercise application access within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Controlled responses do not prove the real service supplies the same result. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The console and browser are real. Controlled responses or mock handlers replace service behavior; they do not establish deployed API conformance.

## Must Not Be Doubled

The console interaction and displayed result under assertion remain real.