Signatures
Open Settings → Signatures in Thermal →
What it's for
Signatures decides which document types need a signature before they go out, which capture methods count, and the consent wording a signer agrees to. It sits above every document Thermal issues — rental and lease agreements, quotes, invoices, work orders, inspection reports, and service agreements — as the one policy table each of those checks (or, for most of them today, doesn't yet check) before issuing.
Reach it from Settings → Signatures in the sidebar, at
/settings/signatures.
Tabs
This screen has no tabs. It's one table, one row per document type.
Panels and controls
Standing note
Above the table: rental and lease agreements require a signature out of the box, and issuing one is actually blocked until it's signed. Every other document type listed — quotes, invoices, work orders, inspection reports, service agreements — issues the same way regardless of what's set here, because enforcement isn't built for them yet; their "Required before issue" option is disabled for that reason. Published versions are never edited — saving a change publishes the next version, so a signature already taken stays tied to the wording that was in force when it was signed.
The policy table
Columns: Document, Signature (a Required / Not required badge for enforced types, or Not enforced yet for types that don't check a policy), Accepted methods, Consent (the consent version label), Policy version (a version number, or Thermal default if nothing's been published for that type yet), and Policy — an expandable editor.
Opening Set policy or Publish new version in the Policy column reveals: Signature (Required before issue / Not required — disabled for document types that aren't enforced), Accepted methods (Typed or drawn / Typed name only / Drawn signature only), Consent version (a label so a past signature stays traceable to the wording that was in force), Consent wording (the actual text a signer agrees to), and Reason for this change — required every time, since every save creates a new version rather than editing the last one. Publish version submits it.
If your org has no signable document types configured, the table shows "No signable documents configured."
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Document type | Fixed — one row per supported type | — | "Pick a supported document type." if the submitted value isn't recognized |
| Signature required | Required before issue / Not required | Yes | Disabled and locked to "Not required" for document types where enforcement isn't built yet |
| Accepted methods | Typed or drawn / Typed name only / Drawn signature only | Yes | "Pick a supported set of signature methods." |
| Consent version | Free text | Yes | Labels the wording below for traceability |
| Consent wording | Free text | Yes | The text a signer sees and agrees to |
| Reason for this change | Free text | Yes | Recorded with every published version |
Only an owner can publish a version — anyone else attempting to submit gets "Only an owner can change the signature policy."
How to configure it
- Turning Required before issue on for rental and lease agreements is already the default and already enforced — issuing is blocked without a signature. No other document type can be set to "Required" yet; the control stays disabled for them until that enforcement is built.
- The Consent wording you publish here is exactly what a signer sees at capture time — there's no separate template elsewhere.
- Because publishing always creates a new version rather than editing the last one, a past signature's consent language is never retroactively changed by a later edit.
Who can see it
- Owners can view and publish new signature policy versions for every document type.
- Office managers have access to the Settings area and can view this table, but the Policy column shows "Owner only" instead of the editable control — a note on the page also says only an owner can publish a new version.
- Dispatchers and technicians cannot reach Settings at all.
The full role matrix is on Roles & permissions.