Verification matrix

Deployed baseline

Reference data was read from the container for platform commit 01e411fddde62e47724862964902b82e9ad47421. See audit methods and remaining checks.

Audited 31 role scenarios and 110 forms, with 916 validation assertions. See individual results below.

Role checks in a disposable environment

Each provisioned test identity received one built-in role or no workspace role, completed MFA, and used the pinned application over HTTP. Status 302 means the Agent workspace redirected the signed-in account. HTTP 200 establishes that the shell opened. Domain records and actions apply additional policy.

Registered forms

Each form was checked against the built-in validator. The collection result is a separate administrator HTTP read. Technical registries can require specialized routes and may lack a generic create action.

Form collections by role

Recorded 3410 role and collection combinations. The individual form references show the observed read statuses. A denied response can be the expected result. A successful response does not establish row or field visibility, a browser form interaction, or a write permission.

Workflow checks

Findings from the live demo

Reading a failed or incomplete check

The earlier audit found a normal change returned HTTP 500 if its CAB meeting was missing. The current release reports this condition as a client validation error. The workflow table above shows the current disposable authorization check. Earlier targeted API results used the migrations packaged in the tested image.

Connector contract tests

Twenty-six assertions passed against the pinned application image using simulated provider responses. These covered cloud connector identity and pagination, ERP submission outcomes, and software deployment approval and status. Live provider authorization, the external effect, and final receipts require their own acceptance tests.

Targeted workflow tests

The baseline audit ran 109 checks successfully using disposable PostgreSQL. Coverage included federation and identity policy, the portal, employee lifecycle, asset assurance, stockroom transfers, supplier governance, outage, customer case and field service workflows. The total includes 26 fixture-based connector checks.

Browser and live acceptance limits

The initial Chromium baseline passed 14 of 15 scenarios using the packaged application. The HR staff scenario stopped at the Category field. The current intake provides recovery controls for a failed queue or catalog read. The HR guide explains the expected behavior and how to check the resulting case and handoff.

Current release verification

Open the follow-up workflow report and screenshots for browser results, role-specific assertions and provider acceptance status.

The live demo has no configured SAML or SCIM connections, and Teams was not configured during the audit. The latest AWS, Google Cloud and Azure billing syncs showed failures. Use the integration guides to test credentials, a scoped operation, and provider-side evidence before enabling a connector for users. Contract checks with simulated responses cover how Qintorava handles those responses.