> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/markup/reference/sealed-job-email.md).

# Sealed Job Email

When you click `Return Sealed Drawings`, Paragon emails the customer informing that the job has been sealed, with links to download the files.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2FyNkWzQDfBGpx3j9GdXVc%2Fmarkup_sealed_job_email.png?alt=media&#x26;token=03176559-537f-4992-9794-e264cb31b46c" alt="Paragon email saying a job has been sealed, with Download PDF, Download Separate PDFs, and Download All Job Files buttons and a Notes section" width="360"><figcaption><p>The sealed job email</p></figcaption></figure>

## Who gets it

* The person who created the job, and, if it's different, the job's contact email. The contact email can list several addresses.
* It comes from <help@paragontruss.com>. When the customer replies, the reply goes to you, the engineer who returned the job.
* You don't get a copy.

Each time you return the job, the email is sent again.

## What's in it

| Item                     | What it is                                                                                                                                                           |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Job name                 | The job that was sealed, such as "Training Plan 2 (Hip) has been sealed."                                                                                            |
| `Download PDF`           | All the sealed drawings merged into one digitally certified PDF, named "ParagonJob\_\<job ID>\_\<job name>.pdf".                                                     |
| `Download Separate PDFs` | A .zip file with each sealed drawing as its own PDF.                                                                                                                 |
| `Download All Job Files` | A .zip file with the sealed PDFs, the component design files, such as .tre and .ans files, and the miscellaneous files.                                              |
| Notes                    | Your `Truss Design Modifications` notes, one line per PDF, as "\<PDF name>: \<notes>". The email also says some files might have changed after the job was uploaded. |

For general questions, the customer can contact Paragon Customer Support at <help@paragontruss.com>. The job summary isn't in the email; it's in Paragon Review. See [Download a Job's Files](https://docs.paragontruss.com/review/how-to-guides/download-a-jobs-files) in the Paragon Review docs.

## The rejection email

When you click `Reject Drawings`, the same recipients get an email with the subject "\<job name> (#\<job ID>) Rejected". Its body is your `Truss Design Modifications` notes, so write the reason there first.


---

# 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://docs.paragontruss.com/markup/reference/sealed-job-email.md?ask=<question>&goal=<user_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.
