> 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/modify-templates.md).

# Modify Templates

Template modifications allow you to change the placement of your seal, signature, or date, customize the cover and back pages, and organize your templates into groups. Changes you save to a template apply to every job you seal after that.

## How Markup chooses a template

Templates are saved at three levels: yours, your organization's, and Paragon's built-in system templates. The template list shows the level after each name, such as `CoverPageTemplate (System)` or `Stamping-MiTek-Portrait (Organization)`. You can't change a system template, but you can save your own copy under the same name.

When you seal a job, Markup looks for each template by name, in this order: your own template, then your organization's, then the system template. So an organization template named `CoverPageTemplate` replaces the built-in system cover page for everyone in your organization. The grid page is the exception: Markup always uses the system `GridPageTemplate`.

## Update or Save New

| Button     | What it does                                                                 | Use it when                                                                |
| ---------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| `Update`   | Replaces the contents of the current template with the selected annotations. | You're changing a template you already saved.                              |
| `Save New` | Saves the selected annotations as a new template.                            | You're saving a template for the first time, or copying a system template. |

`Update` changes the template shown in `Current Template` under `Annotation Tools`. Verify that it shows the correct name, not "None", before you click `Update`.

## Move the seal, signature, or date

### 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)`

`Current Template` changes to the template's name.

### Step 4 - Click `Without Translation`

### Step 5 - Drag the variables to their new locations

Move one at a time, or multi-select and move them together.

### Step 6 - Select all the template's annotations

{% hint style="success" %}
Tip

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

### Step 7 - Click `Template Tools`

### Step 8 - Click `Update`

Confirm when you're asked. The change applies to every job you seal from now on.

## Customize the cover page and back page

### Step 1 - Click `Available Templates`

### Step 2 - Select `CoverPageTemplate (System)`

### Step 3 - Click `Without Translation`

The cover page's annotations and variables appear on the page.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2FkrRrzttNJ9FBLA7bC2YL%2Fmarkup_cover_page_template.png?alt=media&#x26;token=e0b4c58b-7268-4299-8c13-33819dd2b923" alt="The system CoverPageTemplate applied without translation, showing its variables on the page, with Current Template: CoverPageTemplate and the Save New button under Template Tools"><figcaption><p>The system cover page template, ready to save as a copy</p></figcaption></figure>

### Step 4 - Select all the cover page's annotations

### Step 5 - Click `Template Tools`

### Step 6 - Click `Save New`

### Step 7 - Enter `CoverPageTemplate` in `New Template Name`

Use exactly this name, with no spaces.

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

### Step 9 - Choose your group, such as `Seals` for `Assign to Group`

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

### Step 11 - Delete the annotations from the page, then repeat steps 1 to 10 for `BackPageTemplate`

The back page is laid out for a landscape page. If you can't select its annotations, click `Enable System Annotation Editing` under `Template Tools` first.

### Change your cover page

Once your cover page is an organization template, add your logo, text, or [variables](https://docs.paragontruss.com/markup/reference/markup-variables) such as `$jobName`, `$address`, or `$designCode`, then select everything and click `Update`.

* A variable populates with job data only when it's the entire text value of a text box. Put a label such as "Job:" in one text box and `$jobName` in another. (e.g. `Job:` `$jobName` )
* An annotation variable for which the job has no value displays nothing on the sealed drawing.
* Annotation text with no variable is always printed as typed, so leave job-specific fields blank or type them in on each job.&#x20;

{% hint style="info" %}
Note

A cover page template is one page. For a second cover page, such as a legal or disclaimer sheet, save a second template named `CoverPageTemplateExtended`: each region then gets two cover pages. For anything longer, add the pages to each job as a PDF. See [Annotate Drawings](https://docs.paragontruss.com/markup/how-to-guides/annotate-drawings).
{% endhint %}

## Organize templates with the Template Manager

### Step 1 - Click `Template Manager`

It's under `Annotation Tools`. The Template Manager opens full screen.

<figure><img src="https://584518559-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvjCN6yGVi9EoF95QNivD%2Fuploads%2Fcgk6ySvE2uReoPTYgsv4%2Fmarkup_template_manager.png?alt=media&#x26;token=f8bb4daf-887e-4f2f-9556-9e26e2a7c689" alt="Template Manager with All Templates on the left, each with Rename, Delete, and Assign to group icons, and All Groups on the right with Rename Group, Delete Group, Create Group, and the selected group&#x27;s templates"><figcaption><p>The Template Manager</p></figcaption></figure>

* `All Templates` lists your templates and your organization's, with each one's group. System templates aren't listed. Each row has a pencil (`Rename`), a trash can (`Delete`), and an arrow (`Assign to group`), which adds the template to the group selected on the right.
* `All Groups` lists your groups, with `Rename Group`, `Delete Group`, and `Create Group`. Deleting a group leaves its templates unassigned.
* `Selected Group's Templates` lists the templates in the selected group. The arrow next to one (`Remove from group`) takes it out of the group. Removing the last one deletes the group.

### Step 2 - Close the Template Manager

Your changes are saved when it closes.

## Fix a template while you're sealing a job

If a cover or back page looks wrong after you click `Seal Job`, you can fix the template without resealing.

### Step 1 - Click `Template Tools`

### Step 2 - Click `Enable System Annotation Editing`

### Step 3 - Correct the page

### Step 4 - Click `Available Templates` and select the template you're fixing

`Current Template` must display the desired template's name, or pressing `Update` applies changes to a different template.

### Step 5 - Select all the page's annotations

### Step 6 - Click `Update`


---

# 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/modify-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.
