Approval Workflows & Official-Use Fields
Route submissions through reviewers and approvers, with fields only your staff can fill.
Approval Workflows & Official-Use Fields
Turn any form into a controlled process: respondents submit, your staff review and approve, and every action is recorded in a permanent audit trail.
Turning It On
- Open your form → Settings → Submission → Approval workflow
- Choose a mode:
- Review then approve — a reviewer must mark the submission reviewed before an approver can decide
- Approve only — a single approval step
Official-Use Fields
Any field can be marked Official use only in its properties panel. Respondents see it on the public form as a locked field ("Completed during review") — they can never fill or submit it.
For each official field you choose:
- Filled by — the reviewer stage or the approver stage
- Value — typed manually, or auto-stamped from the workflow record: reviewer name, review date, approver name, or approval date. Auto values come from the signed-in account — nobody types their own name.
- Required to complete the stage — the stage cannot be completed while the field is empty (enforced on the server, not just in the browser)
How a Submission Flows
- A respondent submits the public form
- The submission appears in the Pending review queue on the responses page
- A reviewer (any team member) opens it, fills the reviewer-stage official fields, and marks it reviewed — reviewer name/date fields are stamped automatically
- An approver (editor or admin) confirms: they can amend reviewer fields, must fill their own required fields, and then approve or reject
- Approval can trigger a webhook to your downstream system with all official answers included
The queue chips at the top of the responses page (Pending review / Awaiting approval / Approved / Rejected) always show where everything stands.
The Audit Trail
Every review, approval, rejection, and reset is written to a permanent audit record — who acted, when, any notes, and the official values they entered. Resetting a submission's workflow clears its current state but never erases the history.