Run a client acceptance session
Open Acceptance Runs in Thermal →
Acceptance runs replace spreadsheet UAT hand-offs with an in-app record the client can work in their portal. Staff create a run from a scenario template (today: OKC UAT v2, scenarios S1–S13), publish it to a customer, and watch step status, evidence, and GO / NO-GO sign-off land in one place.
Automated Playwright results can feed in as Suggested pass/fail only — they never become the human result, and they never count as sign-off.
Create a run
- Open Acceptance runs (Customers group in the sidebar).
- Select New run.
- Name the run, pick the scenario template, and optionally assign a customer (required before the portal can see it).
- Create — every scenario step is snapshotted onto the run so a later script edit cannot rewrite what the client already saw.
Work the run (staff)
The master rail lists runs by status. Opening a run shows:
- A status stepper (Draft → In progress → Complete)
- A five-cell fact strip (org, scenario set, created, step count, pass rate)
- The step table with pass/fail actions, notes, and evidence thumbnails
- Suggested automated-check results surfaced through InsightRecord — confirm or clear them; never auto-applied
- Sign-off panel for attributed GO / NO-GO by party (Thermal, FieldBoss, OKC, client, …)
Publish to portal moves a draft with a customer into in-progress so the client can act. Export evidence downloads a markdown artifact of the live run (steps, evidence links, sign-offs) for client hand-off until the shared docx generator lands.
Client portal
Customers open Acceptance in the portal to mark steps pass/fail, attach photo evidence, leave comments, and record their own GO / NO-GO. They only ever see runs published to their own customer record — org and customer scope are enforced on every read and write.
Automated checks
Paste a Playwright manifest JSON into the run detail, or set
ACCEPTANCE_RUN_ID + ACCEPTANCE_RUN_ORG_ID when running
okc-uat-full.mjs / ingest-acceptance-run-manifest.mjs. Results land as
Suggested. Turning the acceptance-run automation module to Off is a
real kill switch that blocks ingestion.