> 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/changelog/1.6.4.md).

# 1.6.4

2026-09-01

## What's Changed

### \[Approvals] Export Approval Data to CSV

Approval data can now be **exported directly from the Approvals table tabs as a CSV file**.

* Previously, users could only review this information within HIVO. With the new **Export CSV** option, approval data can be easily downloaded and worked with outside the platform.
* This makes it easier to **review, filter, organise, and share approval information**, or keep a copy of the Approval table data for further reference.

**🔹 How to export:**&#x20;

Go to **Approvals** → select the relevant tab → click the **Export CSV** icon.

👉  **Note:** Your ability to view and export data from each Approval tab depends on your **permissions for the corresponding Approval type**. You can only export data from Approval tabs that you have permission to access. For more information about Approval permissions, see the [**Approvals**](https://support.hivo.co/approvals) guide.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FQ9gyu149z2CYZsLMIF4q%2FGroup%201107.png?alt=media&amp;token=fc40ba61-47d0-4c12-ac8a-ff5c28267671" alt=""><figcaption></figcaption></figure>

***

### \[New Feature] Uploader - Clickable Links in Metadata Field Descriptions

Metadata field descriptions in the Uploader can now include clickable links, making it easier to provide users with additional instructions, reference materials, or supporting resources while they are completing metadata.

**🔹** For example:

* If a Metadata field requires users to follow a specific naming convention, select information based on an external reference, or read additional guidance, a URL can be added directly to the field description.&#x20;
* Users can simply click the link to open the relevant resource in a new tab without interrupting their upload.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FrNOChHr2hXRE9iexOBSD%2FGroup%201109.png?alt=media&amp;token=856a1d0d-ba09-4090-a651-92887b6e65e1" alt=""><figcaption></figcaption></figure>

**🔹 Configure a link:**

* **Client Admins** can add or update the URL in the Metadata field description from [**Metadata Settings**](https://support.hivo.co/client-profile/client-profile-settings/asset-and-metadata-management/metadata-settings).&#x20;
* Once configured, the URL will automatically appear as a clickable link in the corresponding Metadata description when users complete metadata in the Uploader.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FN2Pu4PTUx4kW8Rr03MWZ%2FGroup%201109%20(2).png?alt=media&amp;token=98fbc475-6ffe-4f54-9b6c-84c218be6afd" alt=""><figcaption></figcaption></figure>

***

### \[New Feature] Create Products with Metadata from Product Selectors

We’ve enhanced Product creation from **Product selectors**, allowing users to create more complete Product records directly within their current workflow.

#### **🔹** What’s new?

This is an **Additional Feature** and must be enabled option *"Include creation form for Add Product"* in Client Features Settings by a **Super Admin or HIVO Admin.**

Once enabled:

* When users type a new ID in a **Product selector**, HIVO opens the **full Product creation form**, including configured metadata, instead of adding the ID directly.
* The two existing **Metadata sections are now combined into a single one**, providing a simpler and more consistent experience when entering Product information.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FjCKTfF7SautfJIUxMQlj%2F0922.gif?alt=media&amp;token=26229e4a-09d9-4411-bb28-ebd1c6e736d7" alt=""><figcaption></figcaption></figure>

#### **🔹** Why is this useful?

* Users can capture Product metadata at the time of creation, helping reduce additional steps, improve data consistency, and simplify the Product creation experience.
* Available from Product selectors in **Asset Uploader, Asset Detail, Library Actions, Asset Approvals, and Collections – Related Products**.

***

### Track Asset History from HIVO Connectors

We’ve enhanced **Asset History** to capture asset usage from integrated software connected through **HIVO Connectors**.

#### **🔹** What’s new?

When an asset is **downloaded or embedded** into supported third-party applications via a HIVO Connector, the activity is now automatically recorded in the asset’s **History**.

* This includes integrations such as **Adobe tools, Figma, Canva, Microsoft Word, and PowerPoint**.
* This provides a more complete view of **where and how assets are being used**, including activity that happens outside HIVO. It helps teams improve **asset usage tracking, reporting, and auditing** across connected applications.

👉 Note:  To view the Asset History report:

* Go to Report -> select view **History**
* Only users with a **“Can View Reports Page"** permission to access **Reporting page.**&#x20;

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/changelog/1.6.4.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.
