> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/designer/assets/asset-hierarchies/settings-and-versioning.md).

# Settings and Versioning

Every Asset Hierarchy in Tricloud Nexus includes a **Root Node**, which contains key hierarchy settings and revision (versioning) information.

### Hierarchy Settings

When you select the root node of any asset hierarchy, you gain access to settings that define the identity and data context of the hierarchy. The following properties can be configured:

Settings that can be edited include:

* **Name** The display name of the Hierarchy
* **Alias** An optional [ISA-95 Alias](/management-portal/designer/assets/asset-hierarchies/isa-95.md) to use for the root node. Aliases are used in hierarchical tag naming conventions.
* **Description** Optionally provide a description for the hierarchy to clarify its purpose or scope.
* **Data Store** Select the [data store](/management-portal/platform-settings/data-stores.md) where the asset hierarchy and all associated metadata will be synchronized. The chosen data store also determines where all measurement data will be ingested. \\

<figure><img src="/files/wla2H3nYoDml5MtvYyR9" alt="" width="375"><figcaption><p>Settings of the Asset Hierarchy</p></figcaption></figure>

### Versioning of Asset Hierarchies

At any point during editing, you can [validate and save](/management-portal/designer/assets/asset-hierarchies.md#validate-and-save-hierarchies) your asset hierarchy to ensure structural integrity and catch configuration errors before deployment.

All asset hierarchies in Tricloud Nexus are versioned. Each time you save changes, a new version is saved in the Hierarchy Revisions section, allowing you to:

* Track changes and maintain a history of your hierarchy over time.
* Roll back to previous versions if needed.
* Audit modifications for compliance and troubleshooting.

Versioning provides robust change management, ensuring you always have control and visibility over the configuration of your digital environment.

#### Accesssing Hierarchy Revisions

You can find the Hierarchy Revisions by selecting the root node of the hierarchy. Hierarchy revisions should appear in the right panel of the screen:

<figure><img src="/files/aoPRfpYNTyWBXIyfsKds" alt=""><figcaption><p>Hierarchy Revisions shows who made changes to the hierachy and shows comments for every save action</p></figcaption></figure>

{% hint style="info" %}
You can use the 'Search changelogs' textbox of the Hierarchy Revisions table, to search for changes made by specific users, or specific comments that were added in a previous version of the asset hierarchy.
{% endhint %}

The panel in the right side also contains a Tab called Properties, that allows you to add additional [Meta data properties](/management-portal/designer/assets/asset-hierarchies/meta-data.md) for your Asset Hierarchy.

#### Roll back to previous version

If you need to revert to an earlier configuration (earlier version of the Asset Hierarchy)

* Use the **Asset Hierarchy selection dropdown** to choose a previous version.

<figure><img src="/files/r5pW0PBDsUhcZpRF9KV1" alt="" width="212"><figcaption><p>The Asset hierarchy selection dropdown</p></figcaption></figure>

* Make any necessary adjustments, then **click** **save** to create a **new revision**.

This flexible approach ensures you always have control and visibility over your digital environment and can confidently manage changes as your operations evolve.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tricloudnexus.io/management-portal/designer/assets/asset-hierarchies/settings-and-versioning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.