Users, roles, groups, resources and workflows in editable JSON.
Technical demonstration
Synthetic data · independent implementation · repeatable test scenarios
Access and workflow validation
RBAC · approvals · state transitions · negative scenarios
Buyer outcome: repeatable expected/actual scenario package, discrepancy list with evidence and a PASS/FAIL report against agreed rules.
First scope: permission-structure export, data sample or test environment. Responsibility covers the agreed rules, scenarios and acceptance report.
RBAC → transitions → approvals → expected/actual comparison.
Missing role, conflict, skipped state or missing required approval.
Discrepancy report, structured evidence and PASS/FAIL.
The test passes when the decision and rule match the agreed expectation.
Acceptance package
Expected behavior against the rule decision
DENY is a refusal decision. A test expecting DENY and receiving DENY has a PASS result.
REFERENCE / BASELINE
The reference configuration does not grant employees administrative permissions. The reference package gives 19 PASS results. The controlled-change button verifies regression detection.
For a technical reviewer
Inspect input, rules, run identifier and evidence in the tabs below.
Run the reference package. Correctly detected denials meet the PASS criterion.
What you can verify here
RBAC and inheritance evaluation, transition rules, negative scenarios, expected and actual results, discrepancy evidence and a repeatable PASS/FAIL report.
Acceptance criteria
Agreed test set: all scenarios PASS. Controlled permission change: one discrepancy. Repeating identical input: the same result and run ID. Export: as many results as executed scenarios.
Public scenario parameters
The demonstration input is a controlled export of users, roles, approvals and workflows. An adapter to the source environment is a separate integration scope. Execution covers evaluation of the export; directory administration and production permission changes require a separate implementation agreement.
The workflow path is evaluated against explicit input versions. The report documents evaluation of a specific data version. Reports are isolated by browser session.
Describe the scope