> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/build-and-publish-your-job-approval-form.md). # Build and publish your Job Approval form The Job Approval Form tab controls the questions customers answer from Job Approval outreach. Find it at Settings -> Automations -> Job Approval Form. It appears for any user who can manage Automated Outreach settings. Every business starts on Essential's shared platform default. Essential can improve that default over time, and businesses that have not published a custom form receive those improvements automatically. The form graph is organized into three placements: * **Before properties** runs once before the customer reviews properties. * **Repeated per property** is one repeated region that runs for every property. Each property path must include exactly one Approval decision and finish at **Property complete**. * **After properties** runs once after every property is complete and finishes at **Submit**. Each placement contains named steps, and each step contains blocks. The graph opens in **All steps** so the complete form stays visible; **Previous** and **Next** are disabled in this view. Use **Focus first step** to begin at the start, then **Previous** and **Next** to step between individual steps, or **View all** to return to the full-graph view. Use **Add step** to choose a placement, select a step, and then use **Add block**. Connect block paths in the graph to control the customer order. The editor offers only block types and route targets valid for that placement. Outlined system-flow markers show where the journey begins, repeats for each property, continues after all properties, and ends. Dashed paths connect those markers to customer-facing blocks. Select a block to edit its customer-facing content, options, semantic answer binding, or routes. Each customer-visible content region has one rich-text editor; headings are formatting within that editor, not separate fields. Use it for paragraphs, headings, lists, emphasis, links, and supported variables. Add separate content only for a **Callout** or generated content such as a property list. Property Access uses **Confirm access** and **Update access** tabs because those are mutually exclusive customer states. Select **Settings** to choose each phase entry and edit the **After submission** message. Use the **Standard** and **When a property is declined** tabs to edit those mutually exclusive outcomes; add **Declined properties** to the declined variant to show the affected addresses. Each tab previews only its selected outcome. The shared platform default keeps the existing customer experience and starts with the approval question. Add a **Covered work** block when you want the form to show the asset groups and services frozen into the request. Choose **Cards** to group services under each asset group or **Compact list** for one flat list. **Advanced** can replace either built-in appearance with a custom row using the listed variables. The **Billing destination** block can require an email address or accept flexible text such as a portal or mailing destination. Turn **Collect billing instructions** on only when customers should also provide separate invoicing instructions. **Templates** contains healthy starting points such as Quick approval and Approval with billing. Using a template replaces the local editable draft only. Review it and choose **Save draft** when you want to persist it; selecting a template never publishes or activates a form. Use **Save draft** while you work. Changes remain local until you explicitly save, and the page warns you before leaving with unsaved changes. Saving a draft does not opt your business out of platform-default improvements, and a draft never changes a form that has already been sent. **Preview** walks the draft as a customer would see it. Validation lists missing or invalid paths and takes you to the affected block or form setting; fix those issues before publishing. Choose **Publish** when the draft is ready. Publishing creates an immutable custom version and activates it for future Job Approval outreach. Your custom version then takes precedence over the platform default. Published history lets you activate an older custom version, restore one into a new draft, or choose **Use platform default** to receive Essential's current and future default improvements again. Forms already sent stay pinned to the exact version they were sent with. Opening a form link while signed in to Essential opens the live form with its normal actions. Viewing it or entering answers does not lock an unsent form to that version. Using **Organize these details** or submitting a response pins the form and uses the normal live response flow. Submitted responses are real. A form already pinned keeps its existing version. Customer visits, including customers signed in to the customer portal, continue to lock the form to the version they receive. If your Essential session expires, sign in again to continue to the form. The Property access synchronization card is separate from the form graph. When enabled, an accepted customer correction can update the property's access information after the configured safety checks; turning it off leaves the customer's response on the resulting task without changing the property. > **Where to find it:** Settings -> Automations -> Job Approval Form tab ## Related guides * [Configure the automated outreach sequence](/administration/settings/configure-the-automated-outreach-sequence.md) * [Set the confirmation email for automated outreach](/administration/settings/set-the-confirmation-email-for-automated-outreach.md) * [Where to see customer approvals and responses to service requests](/field-operations/tasks/where-to-see-customer-approvals-and-responses-to-service-requests.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.withessential.com/administration/settings/build-and-publish-your-job-approval-form.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.