> 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-templates/managing-parameters-with-associated-rights.md).

# Managing parameters with associated rights

Manage parameter access rights in VHQ with role-based restrictions, sensitive value masking, and support for POINT Format across multiple containers.

<details>

<summary>Keywords</summary>

Also called: parameter access rights, MaskValue. Search terms: masked parameter, POINT format.

</details>

## What are parameter access rights?

In VHQ, parameter rights restrict viewing or editing parameters based on the access level defined in the parameter form view file. This lets you hide or show parameters for specific users. Beyond hiding, showing, or allowing edits, VHQ can also restrict a parameter's displayed value, even for users with view access.

{% hint style="info" %}
If a parameter value is a password, other users can't see it, even if they have view or edit access.
{% endhint %}

## Masking parameter values

A **MaskValue** attribute, next to the *Access* attribute in VPFX XML, controls masking. If set to *True* (case-insensitive), the parameter value is masked with asterisks (\*\*\*\*\*); if *False*, it's unmasked.

A user with add permission can define and add a value to the parameter regardless of masking. A user with modify permission can edit the value and restore it to default, but can't see the modified value — that's the expected masking behavior. Masked parameters can't be deleted.

{% hint style="info" %}

* Users can't copy a masked value.
* Masking only applies to parameters with a *String* value type.
* If *MaskValue* isn't set to a valid Boolean in the form view XML, it defaults to unmasked, and the form file upload is rejected with *Invalid file format*.
  {% endhint %}

## POINT Format support

**POINT Format** support is a newer feature that manages multiple containers with a single XML file, reducing multiple downloads to one.


---

# 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-templates/managing-parameters-with-associated-rights.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.