> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-template-pt-at-hierarchy.md).

# Configuring parameter template (PT) at hierarchy

Assign parameter templates to reference sets at hierarchy levels to apply parameter values across multiple devices under the hierarchy with download automation and inheritance options.

{% hint style="info" %}
**Use this when** you need to apply a parameter template to every device under a hierarchy node, via a reference set.
{% endhint %}

You can assign a reference set to a hierarchy, and VHQ lets you assign parameter templates to that reference set. Reference sets can be inherited or directly assigned at the hierarchy level. All devices under that hierarchy which qualify for the reference set also receive parameter values from the assigned parameter templates (PT).

{% hint style="info" %}
To configure a PT at hierarchy level, you must already have a PT (see Adding parameter template), and it must be assigned to the reference set.
{% endhint %}

## Assign a reference set to a hierarchy

{% stepper %}
{% step %}

### Open Hierarchy Assignment

Go to **Device Management** > **Manage Reference Sets** > **Hierarchy Assignment**.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FWcRrAgjYLlBTQJMbeNbr%2Fimage%20(36).avif?alt=media&amp;token=47c69b06-fa02-4c27-b614-c825358b7f21" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the hierarchy node

Select the hierarchy and click the pencil icon. At a hierarchy node, you can assign a parameter template to reference sets directly assigned to that node, and/or to inherited reference sets. Selecting a root hierarchy only offers enabling/disabling download automation; selecting a hierarchy with children also lets you inherit reference sets from the parent (**Yes**/**No**) and enable/disable download automation.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FPV3eCJLsPUDCoqPC9smo%2Fimage%20(37).avif?alt=media&amp;token=69f94832-e1b0-4e0d-b1e0-fd2bfeb7dd8e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FoDYqSN34Sv0QW8YvceEX%2Fimage%20(38).avif?alt=media&amp;token=a98d98f8-f2e7-4470-883d-dd3805891f53" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set the download schedule

Enable or disable automatic downloads for the selected hierarchy with the **Download Automation** checkbox, then choose a schedule:

* **Next contact**: Schedule the download for the device's next heartbeat.
* **Next Available free time slot**: The VHQ server identifies the next free time slot for the download.
* **Maintenance window**: Schedule the download during the device's next maintenance window.
* **Download during maintenance window**: Only download during the maintenance window's free time slot.
  {% endstep %}

{% step %}

### Assign reference sets

The *Reference sets* tab lists reference sets available from the hierarchy. Assign multiple reference sets to a hierarchy node and order them to determine which one qualifies for devices under that path. The *Parameter templates* tab activates once a reference set is selected — changes to the template's parameter values apply to all applicable devices under the hierarchy and its children.

Click **Expand** to view details of the qualified reference sets.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2F7MBSmwRYvJhl6hjwRJ6Q%2Fimage%20(39).avif?alt=media&amp;token=e5768644-8b86-4ffc-bcff-6946cab21d1a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FchM5aU3COd6WEJtIIYGt%2Fimage%20(40).avif?alt=media&amp;token=5fed20b4-f972-4544-925f-217261803c5c" alt=""><figcaption></figcaption></figure>

Click **Save** to assign the reference set to the hierarchy.
{% endstep %}

{% step %}

### Assign parameter templates

The *Parameter Templates* tab lists all templates available to the reference sets assigned to the hierarchy. Select the template(s) to assign to devices under the hierarchy.

A popup confirms how many devices will be affected.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FJzy0kzxQRj5pTm3oP9MK%2Fimage%20(41).avif?alt=media&amp;token=dea811ef-22db-4f26-a02b-62073d53247e" alt=""><figcaption></figcaption></figure>

Click **OK**, then **Save**. Multiple hierarchy templates can be assigned to one node — since parameter templates are mutually exclusive, no ordering is needed. VHQ validates that an assigned template doesn't conflict with any hierarchy template values assigned above (if inherited) or below (if passed down). This validation only runs when **Inherit from Parent Hierarchy** is enabled.

If a conflict is found, VHQ shows: *One or more of the parameters in the template(s) you are assigning conflicts with parameter that is already assigned. For duplicate parameters, click here* — from which you can view the conflicting parameters and instances.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FfjHMbI32VcxuceK7QKlR%2Fimage%20(42).avif?alt=media&amp;token=fdb571c4-e35b-49e6-9793-045dabdc0944" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FVIPcIFGCwgO6m0eYa5z2%2Fimage%20(43).avif?alt=media&amp;token=b4f050b1-01e4-4a1f-b65b-43a1333c57af" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Guidelines

* You can add, edit, delete, copy, and view a parameter template for an application from the *Application Library* screen.
* The *Parameter Template for Application* screen (under **Manage Downloads** > **Application Library** > **Configure**) includes a **Hierarchy Name(s)** column, listing any hierarchies the template is assigned to (comma-separated).

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2Frm7j7xOUK3xwa3EtJdFi%2Fimage%20(44).avif?alt=media&amp;token=9894fc01-d8b0-4334-b7c2-c9b61254e946" alt=""><figcaption></figcaption></figure>

* Only regular (non-hierarchy) templates can be deleted. A hierarchy template must first be unassigned from the hierarchy level before it can be deleted.

{% hint style="info" %}
Unassigning a template from a hierarchy's reference set restores default parameter values on affected devices. You can't overwrite parameter files, VPDX, or VPFX files while a parameter template is assigned to the hierarchy — and you can't delete a reference set while a PT is assigned to it.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: hierarchy parameter template, PT at hierarchy. Search terms: hierarchy assignment, reference set conflict.

</details>


---

# 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.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-template-pt-at-hierarchy.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.
