---
id: TST-PFM-SEC-015
title: Permissions console checks
kind: browser-lifecycle
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - e2e/dev/permissions.dev.spec.ts
implements:
  - ATS-PFM-SEC-007-02
  - ATS-PFM-SEC-007-09
environment: deployed-dev
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: >-
  Use the suite’s existing disposable identities and workspace fixture boundary; retain shared
  development records.
assertion_evidence:
  - provenance: test
    source: >-
      react-console:e2e/dev/permissions.dev.spec.ts#shows a person with no role the No Access
      screen, and does not loop back to the login screen
  - provenance: test
    source: >-
      react-console:e2e/dev/permissions.dev.spec.ts#hides a domain the tenant has no application
      for, and keeps the one it has
  - provenance: test
    source: >-
      react-console:e2e/dev/permissions.dev.spec.ts#denies a page whose permission nobody holds,
      when its URL is typed
  - provenance: test
    source: >-
      react-console:e2e/dev/permissions.dev.spec.ts#offers the administrator an action it does not
      offer the read-only user
dependency_evidence: >-
  The browser drives the development console using the suite’s configured identities and records.
  Service availability, sign-in prerequisites and fixture cleanup remain requirements for a
  successful run.
evidence:
  - 'react-console:e2e/dev/permissions.dev.spec.ts'
  - >-
    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
---
# Permissions console checks

## Verification Boundary

The file drives the console in the configured development environment. The assertion references identify the source checks for permissions.

## 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 browser drives the development console using the suite’s configured identities and records. Service availability, sign-in prerequisites and fixture cleanup remain requirements for a successful run.

## Must Not Be Doubled

Keep the browser or public request path and the service decisions being claimed real. Any intercepted provider response limits proof at that boundary.