> 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/markup-variables.md).

# Markup Variables

A variable is a text box used in templates whose text starts with `$`, such as `$signature`. When Markup seals a job or applies a template with `To This Page`, it replaces each variable with a value from the job, your account, or your seals. Use them in sealing templates and on your cover page.

* A variable is replaced only when it's the whole text of its text box. "Job: $jobName" isn't replaced; put "Job:" and `$jobName` in separate text boxes (e.g. `Job:` `$jobName`)
* A variable with no value, such as `$subdivision` on a job with no subdivision, displays nothing on the sealed drawing.
* `Without Translation` copies a template without replacing its variables, so you can see where they are placed.

## Seal and signature

These are the variables in the sealing templates. They tell Markup where to place your seal, a signature, and the date.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2Fh79fN7U1NKSqsxLyRlwF%2Fmarkup_signature_variables.png?alt=media&#x26;token=f103c00b-6977-4694-83e5-e9e22cffc79d" alt="A sealing template showing the $seal1, $signature, $date, and $userName variables"><figcaption><p>Seal and signature variables in a sealing template</p></figcaption></figure>

| Variable                           | Replaced with                                                                                                 |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| `$seal`                            | Your seal for the job's first region.                                                                         |
| `$seal1`, `$seal2`, …              | Your seal for the job's first, second, … region. The landscape template has `$seal1`, `$seal2`, and `$seal3`. |
| `$renewalDate`, `$renewalDate1`, … | The expiration date of the corresponding seal.                                                                |
| `$signature`                       | One of your signatures, picked at random, at 90% of the seal's size.                                          |
| `$date`                            | The date the job is sealed.                                                                                   |
| `$time`                            | The time it's sealed, in Eastern time.                                                                        |
| `$userName`                        | Your name.                                                                                                    |

## Job and project

`$jobName` (links to the job), `$jobId`, `$customerName`, `$lotNumber`, `$address`, `$city`, `$subdivision`, `$model`, `$designProgram`, `$designCode`, `$windCode`, `$windSpeed`, `$meanRoofHeight`, `$roofLoad`, `$floorLoad`, `$windExposureCategory`, `$trussManufacturer` (the organization that owns the job), `$designCount`, `$coverPageUrl`, `$backPageUrl`

## Building designer

`$buildingDesignerName`, `$buildingDesignerLicenseNumber`, `$buildingDesignerState`, `$buildingDesignerAddress`, `$buildingDesignerCity`

## You

`$userName`, `$userEmail`, `$userPhoneNumber`

## Page

`$pageNumber`, `$pagesCount`, `$pNumber` (the PDF's P-number)

## Region and certificate of authority

`$state` or `$region`, `$certificateOfAuthorityText`, `$companyNumber`, and numbered versions for each of the job's regions, such as `$state2` and `$companyNumber2`

## Grid page

The built-in grid page lists up to 50 designs, numbered 1 to 50: `$designPNumber1`, `$designUrl1`, `$designName1`, `$designSealDate1`, and so on.


---

# 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/markup-variables.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.
