ReferenceElsewhere in Thermal

Automation system

Open Admin → Workflows in Thermal →

What it's for

Automation system is a read-only look under the hood of what the app can automate: every registered action it's capable of taking, which automation modules exist and what mode each is running in, and a live feed of recent runs and exceptions. It exists so an owner can see exactly what automation is doing — nothing here is a rule you write; it only ever reflects what the app actually does.

Reach it from Settings → Workflows in the sidebar, at /admin/workflows.

Tabs

The page has no tabs. It is stacked sections: registered actions, automation modules, recent runs, and recent exceptions.

Panels and controls

  • If your shop has old drafted automation rules from the retired WHEN/AND/THEN rules editor, a banner names how many are on file and explains plainly that they were never executed by anything — they're kept for the record only. Automation now runs solely through the registered actions below.
  • Registered actions lists every action the app can take, with its Area, Capability, Side effect (read, write, or irreversible), Entity, and internal Registry id. This is the full inventory — what's possible, not what's turned on. No actions registered is the empty state.
  • Automation modules lists each module by name with its current Autonomy mode — Off, Suggest, or Auto. No automation modules configured is the empty state.
  • Recent runs shows the workflow name, what triggered it, its status (running, completed, failed, partial), steps completed, when it started, and how long it took. A failed run is dimmed. No workflow runs yet is the empty state.
  • Recent exceptions shows the workflow name, severity (critical, warning, error), status, the exception message, and when it opened. No workflow exceptions recorded is the empty state.
  • A footer line totals the run and exception counts shown.

What it accepts

This page has no forms. Everything on it is generated from the action registry and the org's real automation settings — there is nothing to submit here.

How to configure it

  • Automations is where a module's Off/Suggest/Auto mode is actually changed — this page only displays the current setting.
  • The registered actions list itself is fixed by what the app builds, not a per-shop setting.

Who can see it

This screen sits behind the Automations area.

Owners and office managers can open it. Dispatchers and technicians cannot — this is an administrative view of the automation system, not a day-to-day work surface. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.

The full role matrix is on Roles & permissions.

On this page