---
id: TST-CRM-REG-036
title: Assignment editor controls and access
kind: unit
product_area: crm
module: regions
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - components/regions/__tests__/assignment-rules-editor.test.tsx
implements:
  - ATS-CRM-REG-013-08
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: In-memory values and test-owned component state.
evidence:
  - 'react-console:components/regions/__tests__/assignment-rules-editor.test.tsx'
assertions:
  - scenario: ATS-CRM-REG-013-08
    source: >-
      react-console:components/regions/__tests__/assignment-rules-editor.test.tsx#who may open the editor
      › is not somebody who may only look, whatever the URL
binding_scope: >-
  Exact assertion anchors identify the contribution of this file. Scenario-level bindings may compose
  several files; registration does not assert that every file alone executes every scenario step.
---

# Assignment editor controls and access

## Verification Boundary

The suite exercises regional calculations, declarations or console components with test inputs. Its assertions do not establish deployed service behavior.

## What This Suite Proves

The linked source assertions contribute checks for direct editor access respects the management gate. A scenario spanning several files relies on those assertions together; this file supplies only its named checks.

## What It Does Not Prove

The register establishes neither a current passing run nor verified conformance. Unbound scenarios, broader feature chains and the delegated infrastructure beyond this execution boundary remain unproved.

## Real Dependencies and Test Doubles

Test inputs, execution contexts, request clients or component dependencies are supplied by the suite. Database persistence and deployed transport are outside this boundary.

## Must Not Be Doubled

The calculation, permission declaration or console behavior under assertion must remain the real implementation.