> 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/before-you-start.md).

# Before You Start

Setting up Markup takes about an hour. To expedite setup, gather the items below before you begin.

## Confirm your account access

Your account requires specific permissions, which must be enabled by Paragon turns on for you. Contact Paragon Support with any questions. See [Set Up a Reviewing Engineer Account (Paragon use only)](https://docs.paragontruss.com/markup/before-you-start/set-up-a-reviewing-engineer-account-paragon-use-only).

| Permission                | What it lets you do                                                       |
| ------------------------- | ------------------------------------------------------------------------- |
| `accounts-access`         | Sign in to Paragon Accounts, where you register seals and signatures.     |
| `seals-signatures-markup` | Register seals and signatures, and use the sealing tools in Markup.       |
| `review-access`           | Sign in to Paragon Review.                                                |
| `markup-access`           | Open jobs in Markup. Without it, `Open Job` is not available from Review. |
| `organization-templates`  | Save, edit, and delete templates for your organization.                   |

{% hint style="success" %}
Tip

With the  `organization-job-contact` permission, you receive an email whenever a job is shared with your organization.
{% endhint %}

## Files to have ready

Download the files Paragon sends you, and unzip everything into one working folder on your computer.

* **A seal image for each state in which you are licensed.** Note each state's license expiration date ahead of time. They differ by state, and you need them when you register each seal.
* **At least one signature image with a transparent background.** Use a .png, not a .jpg: a JPEG carries a white box that shows on the drawing. Upload more than one if you can; Markup picks one at random each time it applies a seal.
* **The sealing template files (.json) from Paragon.** Paragon provides the default templates as a .zip which serve as a starting point for your organization.
* **Two test PDFs, one portrait and one landscape,** provided as a .zip. You use them to create a practice job.

{% hint style="success" %}
Tip

If your signature has a white background, save it as a PNG and remove the white with an image editor or a background-removal tool. An AI image tool asked to "make the background transparent" usually produces a usable file in under a minute.
{% endhint %}

## Next step

[Register Seals and Signatures](https://docs.paragontruss.com/markup/before-you-start/register-seals-and-signatures)


---

# 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/before-you-start.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.
