> 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/how-to-guides/create-and-set-up-sealing-templates.md).

# Create and Set Up Sealing Templates

Sealing templates inform Markup where to place your seal, signature, and date on each drawing. Paragon provides them as .json files. You upload each one and save it as an organization template under its exact name. Markup finds templates by name, so once they're saved, `Seal Job` places everything for you.

You only need to do this once per organization, for the initial setup. You can modify the templates later if anything changes.

Before you begin, open your [practice job](https://docs.paragontruss.com/markup/before-you-start/create-a-practice-job) in Markup, and have the .json template files accessible.

{% hint style="info" %}
Note

Engineers seal drawings; they don't stamp them. Some default template names use the word "Stamping." Leave those names exactly as they are, because Markup identifies them by their exact name.
{% endhint %}

## The templates you need

| Template name               | Used for                                                                  |
| --------------------------- | ------------------------------------------------------------------------- |
| `Stamping-MiTek-Portrait`   | Portrait pages of MiTek jobs, and of any job that isn't Alpine or Paragon |
| `Stamping-Alpine-Portrait`  | Portrait pages of Alpine jobs                                             |
| `Stamping-Paragon-Portrait` | Portrait pages of Paragon jobs                                            |
| `StampingTemplateLandscape` | Landscape pages of every job                                              |

`Seal Job` uses the portrait template from where the job's designs originated, and uses the landscape template for any page that's wider than it is tall. If the required template is missing, sealing stops with "Error sealing job."

Markup also uses `CoverPageTemplate`, `BackPageTemplate`, and `GridPageTemplate`. They're built in, so you don't upload them. To use your own cover or back page, see [Modify Templates](https://docs.paragontruss.com/markup/how-to-guides/modify-templates).

## Upload and save a sealing template

### Step 1 - Click `Add Page`

`Add Page` is the <img src="https://raw.githubusercontent.com/google/material-design-icons/master/png/content/add_circle/materialicons/24dp/2x/baseline_add_circle_black_24dp.png" alt="Add Page icon" data-size="line"> icon in `Document Tools`. It adds a single, blank page after the current page. Most sealing templates are in portrait orientation and therefore, are easiest to work with on a portrait page.

### Step 2 - Click `Upload Annotation/Image` and choose one .json template file

`Upload Annotation/Image` is the <img src="https://raw.githubusercontent.com/google/material-design-icons/master/png/image/add_photo_alternate/materialicons/24dp/2x/baseline_add_photo_alternate_black_24dp.png" alt="Upload Annotation/Image icon" data-size="line"> icon at the end of the second row under `Annotation Options`. Choose one file at a time. The template's annotations appear on the page, already selected.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2FLsllsbYEmwHDW47hwVam%2Fmarkup_upload_annotation_image.png?alt=media&#x26;token=b8f947e3-4c4f-4439-8683-4a639e9f8e27" alt="Document Tools in the Markup left sidebar with the Upload Annotation/Image button highlighted"><figcaption><p>The Upload Annotation/Image button</p></figcaption></figure>

Text that starts with `$`, such as `$seal1`, `$signature`, and `$date`, is a variable. When you seal a job, Markup replaces them with your seal, a signature, and the date. See [Markup Variables](https://docs.paragontruss.com/markup/reference/markup-variables).

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

### Step 3 - Click `Template Tools`

It's under `Annotation Tools`, and opens the template options.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2FsW27S0gVvgZAURy03wd6%2Fmarkup_template_tools.png?alt=media&#x26;token=4c72ab1d-b23e-4524-a064-3de5c94768b4" alt="Annotation Tools section with Template Manager, Available Templates, Current Template, and the Template Tools panel with Save New, Update, Delete, the Apply Selected Template options, Download Selected, and Enable System Annotation Editing" width="225"><figcaption><p>Template Tools</p></figcaption></figure>

### Step 4 - Click `Save New`

`Save New` needs at least one selected annotation. If you clicked away from the template, select all its annotations again.

{% hint style="success" %}
Tip

Press `Ctrl + A` to select every annotation on the page.
{% endhint %}

### Step 5 - Enter the template's exact name, such as `Stamping-MiTek-Portrait` in `New Template Name`

Copy the name from the file instead of typing it: in File Explorer (or Finder on a Mac), select the file, press F2 or right-click and select rename, and copy the name.

{% hint style="danger" %}
Warning

The name must match exactly, including capitals. If it doesn't, `Seal Job` can't find the template and sealing fails.
{% endhint %}

### Step 6 - Check `Make organization template`

Organization templates are available to everyone in your organization who seals jobs. The check box is shown only if your account has the `organization-templates` permission. Leave `Template Type` set to `Other`.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2F0JJ0q5vCLf3fZFPNb1Jt%2Fmarkup_new_annotation_template.png?alt=media&#x26;token=18f1ecaf-eaf0-44b1-9c8b-8785bab073f8" alt="New Annotation Template dialog with the name Stamping-MiTek-Portrait, the Make organization template check box, Template Type set to Other, Assign to Group set to create group, and the Save Annotation Template button" width="180"><figcaption><p>The New Annotation Template window</p></figcaption></figure>

### Step 7 - Choose `(create group)` for `Assign to Group`

A group filters the template list, so you can find your sealing templates quickly. After your first template, choose your existing group instead, and go on to Step 9.

### Step 8 - Enter a group name, such as `Seals`, and click `OK`

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2Fb81BLZqkiisqIxSxi0sU%2Fmarkup_create_group_prompt.png?alt=media&#x26;token=d47d5655-a98a-4562-b75c-770196e2022b" alt="Prompt asking for a name for the new group, with OK and Cancel buttons, over the New Annotation Template window" width="260"><figcaption><p>Naming the new group</p></figcaption></figure>

### Step 9 - Click `Save Annotation Template`

`Current Template` under `Annotation Tools` changes to the template's name.

### Step 10 - Delete the template's annotations from the page

Select them all and press Delete, so the page is clear for the next template.

### Step 11 - Repeat steps 2 to 10 for each of the other sealing templates

When you're done, your group has all four sealing templates.

## Check a template

### Step 1 - Click `Available Templates`

### Step 2 - Choose a group, such as `Seals` for `Select Template Group`

### Step 3 - Select a template, such as `Stamping-MiTek-Portrait (Organization)`

### Step 4 - Click `Without Translation`

`Without Translation` copies the template onto the current page exactly as it was saved, without filling in its variables, so you can see where each one sits. `To This Page` fills the variables in.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2FG5lNwDWbbtgQa5w6uYrt%2Fmarkup_seals_group_without_translation.png?alt=media&#x26;token=4cbbc53a-9dce-4937-b3ed-c093c7bf3b33" alt="Markup with the Seals group selected in the right sidebar showing the four Stamping organization templates, and the landscape template applied to a page showing the $seal1, $seal2, $seal3, $signature, and $date variables"><figcaption><p>The landscape sealing template applied without translation</p></figcaption></figure>

To move any of them, see [Modify Templates](https://docs.paragontruss.com/markup/how-to-guides/modify-templates).


---

# 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/how-to-guides/create-and-set-up-sealing-templates.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.
