> 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/task-documents-send-and-attach-supporting-documents.md). # Task Documents: send and attach supporting documents Task Documents settings control how inspection reports, supporting documents, and job photos are sent or attached from reports and tasks. It's one of five tabs on the Tasks settings page, alongside Task Statuses, Task Status Automations, Jobs, and Custom Folders. There are five toggles. Your changes aren't saved until you use **Save**. **Email inspection reports.** Lets your team email an inspection report while publishing it, from **Send Report** in any open submitted report's "..." menu, or from **Send Report** in a Job task's Inspection Reports section. The report-page and task actions appear after the submitted report has a generated PDF. Turning this off hides direct inspection-report sending across the app. This toggle does not control **Send Job Summary**. Job Summaries publish a no-login recap link that can include an inspection report with the rest of the job, and they are enabled separately in Settings -> Job Summaries. If both settings are on, the Job task offers both sharing methods. **Auto-attach documents to quotes from tasks.** When a quote is created from a deficiency task's Quick Action, the task's inspection report and any work acknowledgments for its job are attached to the quote automatically. This applies however the quote is created from the task — whether you build it yourself and Save, or use Generate draft. **Auto-attach documents to invoices from tasks.** The same, for invoices created from a job task's Quick Action: the job's inspection reports and work acknowledgments are attached automatically. **Auto-attach job photos to quotes from tasks.** When a quote is created from a Job task, the job's photos are offered in the quote's Attachments section. Keep the photos you want and remove any that should not go with the quote. **Auto-attach job photos to invoices from tasks.** The same, for invoices created from a Job task: the job's photos are offered in the invoice's Attachments section so you can review them before sending. Auto-attached documents are added when the quote or invoice is created, so they travel with it when you send it to the customer. They only ever come from the task you created the document from, and only for that task's property. Job photos are presented for review in the new quote or invoice rather than being sent immediately. > **Where to find it:** Settings -> Work Management -> Tasks -> Task Documents ## Related guides * [Quick Actions on a task: create a visit, invoice, or quote without leaving the task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md) * [Download or email an inspection report](/field-operations/inspection-reports/download-or-email-an-inspection-report.md) * [Set up Job Summaries](/administration/settings/set-up-job-summaries.md) * [Add, rename, reorder, or remove task statuses](/administration/settings/add-rename-reorder-or-remove-task-statuses.md) * [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.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/task-documents-send-and-attach-supporting-documents.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.