> 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/review/how-to-guides/edit-a-job.md).

# Edit a Job

Open a job from the grid to see its details, change them, download its files, or open it in Paragon Markup.

## Step 1 - Click a job's name in the grid

The job panel opens above the grid with the job's ID, its details, and how many components, other PDFs, and miscellaneous files it has.

## Step 2 - Change the details you need

You can change the same fields you filled in when you created the job, with these limits:

* You can't add or remove files, or change `Plate Manufacturer`.
* Only the person who created the job can change `Job Comments`.
* `Billing Location` appears only on jobs your organization owns.

## Step 3 - Click `SAVE CHANGES`

To close the panel without saving, click `CLOSE` in the control bar.

## More Actions

* `DOWNLOAD` opens the Download Job window. See [Download a Job's Files](https://docs.paragontruss.com/review/how-to-guides/download-a-jobs-files.md).
* `OPEN JOB` opens the job in Paragon Markup in a new tab. It appears only if your account can use Paragon Markup. If the job's files are still being prepared, Paragon Review shows "Preprocessing is not yet complete." Try again in a few minutes.


---

# 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/review/how-to-guides/edit-a-job.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.
