> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/assets/asset-metadata.md).

# Asset Metadata

Metadata is optional information that may be attached to Assets.

The purpose of metadata is to describe additional information about the Asset that cannot be described with properties like Name, Tags, Collections, etc. All metadata fields are composed of key: value pairs (e.g. Author: John Doe), which can then be searched by in the Library.

To **edit an Asset’s metadata**, navigate to the Asset’s Detail page and click the **Metadata** section. The ‘Add Entry’ button will show you a list of default metadata field options, or you may opt to enter your own using the ‘Custom Entry’ button. Click **Submit** to save your changes.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FdBQEU6d46Oj91PlE3WI0%2Fimage.png?alt=media&amp;token=b34c6876-0694-4721-a1ab-2721e661d7f3" alt="Asset metadata"><figcaption><p>Asset metadata</p></figcaption></figure>

Asset metadata can be viewed in both Asset Previews and the Asset Detail page (under the ‘details’ section) if available.

Admin accounts can set a warning for Users downloading Assets that contain copyright/description/license metadata in the Client Profile => settings => upload/download settings.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FkPPH5a7opjU4q0NMTHqd%2Fimage.png?alt=media&amp;token=20e9635e-a47c-48fe-9365-4512e5fb00e0" alt="Asset usage"><figcaption><p>Asset usage</p></figcaption></figure>


---

# 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://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/assets/asset-metadata.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.