---
id: TST-PFM-OPS-109
title: Application access permission
kind: unit
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/licensing/tests/unit/application-access-permission.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: 'Process-local inputs, registries and test adapters.'
evidence:
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts at
    ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#publishes the
    key for opening Platform
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#publishes that
    one key alone, and none of the five standard actions of a resource with records
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#describes it in
    the words an administrator reads when granting it
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#declares it at
    the read tier, because being let in is the least any user of an application has
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#does not mark it
    staff-only, which would keep it out of every customer\u2019s roles
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#does not mark it
    sensitive: granting a user the application their job is in needs no review
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#generates the
    three tier policies of Platform the key has to reach
  - >-
    services-platform:modules/licensing/tests/unit/application-access-permission.spec.ts#puts it in
    Platform Read Only, the narrowest of them
---

# Application access permission

## Verification Boundary

This suite exercises application licensing through its declared function or structural boundary. 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 permission within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. No complete specification scenario is attributed to this suite yet.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The production logic under assertion is real. Inputs, registries or source files supply the declared test data; no live service workflow runs.

## Must Not Be Doubled

The production function, registry or builder under assertion remains real.