> For the complete documentation index, see [llms.txt](https://docs.geoprismregistry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-tutorial/6.4-content-setup/6.4.3-hierarchies/6.4.3.3-edit-the-metadata-of-a-hierarchy.md).
# 6.4.3.3. Editing the metadata of a hierarchy
{% hint style="info" %}
Registry Administrators can edit metadata for hierarchies for the organization they are a part of.
{% endhint %}
To edit the metadata of a hierarchy:
1. Go to the *Geo-Objects and Hierarchies* module either by clicking the Geo-Objects and Hierarchies module icon in the main menu page or by clicking the hamburger menu () in the upper right corner and selecting *Geo-Objects and Hierarchies*.\\
2. If needed, expand the *Hierarchies* column on the sidebar by clicking the arrow at the end.\\
3. Scroll down the *Hierarchies* column to the organization you are a part of. Find the hierarchy you want to edit the metadata of and click the **Edit** button () beside its name.\\
4. The *Edit Hierarchy* window will open. Edit the hierarchy metadata as necessary.\\
5. Click the **OK** button.
---
# 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.geoprismregistry.com/readme/current-1/geoprism-registry-tutorial/6.4-content-setup/6.4.3-hierarchies/6.4.3.3-edit-the-metadata-of-a-hierarchy.md?ask=&goal=
```
`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.
