> 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.5.md).

# 1.6.5

2026-09-15

## What's Changed

### \[New Feature - Approval] Filter Unassigned Appearances by Tags

You can now **filter Unassigned Appearances by Tags** in **Approvals > People > Unassigned Appearances tab**.

Previously, the search bar only supported searching by **asset name or folder**. 

With this update, you can:

* Enter Tags such as “HIVO” or “demo” to quickly narrow down appearances associated with relevant assets.
* Use the **View Settings** (gear icon next to Filter) to quickly narrow down results by selected Tags.

This makes it easier to find and review relevant unassigned appearances, especially when working with a large number of assets.

⚠️ **User Right Required:** You need the following permissions to **access the People page**: "Can View Recognition Profiles on the People page" and "Can Tag Faces in Any Asset". 

👉 You can explore more here:

{% @howdygo/embed url="<https://app.howdygo.com/share/1244acb0-29f9-4b06-8411-f85efc587e25>" %}

***

### \[Notification - Asset Approval] Notifications for Approval Owner Comments

Approval Owners can now receive a notification **whenever a new comment is added to an asset they own**, helping them stay updated on feedback without having to manually check the approval.

This notification is controlled by the new setting: **“When someone comments on an asset for which I am an approval owner.”**

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FvSkCKJXZb3o4vCkT2oJD%2FGroup%201114.png?alt=media&amp;token=81773604-c45b-4132-9a27-b1ed499b9b35" alt=""><figcaption></figcaption></figure>

👉 **How to configure:** Go to **Settings -> Global Notification Settings** **-> Approval Notifications.**

> **Note:** Notifications for comments marked as **“Request Changes”** by External Approvers are already supported through the existing **“I have been assigned on an Asset approval to-do list”** notification setting.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FMjbRO1cQYS4npe3V77y1%2FGroup%201113%20(2).png?alt=media&amp;token=6fac609e-4b60-4ea9-ab27-2fe4476c7b43" alt=""><figcaption></figcaption></figure>

***

### \[Enhancement] Improved Retention & Disposal Approval Records

Retention & Disposal approval records now display the **action performed** directly in the record details.

This provides clearer visibility into what action was taken, making it easier to review and understand the history of Retention & Disposal approvals

👉 **How to view: Approval -> Record tab -> Open Record Approval details** (click on Batches) -> see **Action Field**.&#x20;

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FilIQTof88pMpNS2Ehzwn%2FGroup%201115.png?alt=media&amp;token=9a3a8945-6f3b-4fb5-afc7-7c756b20cacf" alt=""><figcaption></figcaption></figure>

***

### \[Improvement] Brief Template Settings- Add Placeholders to Brief Template Fields

You can now add **placeholder text** to fields in **Brief Templates**, helping users understand what information should be entered.

* Placeholders are available for the following field types: **Text, Number, Address, and Select**.
* The placeholder is **blank by default**.&#x20;

{% @howdygo/embed url="<https://app.howdygo.com/share/4c27136b-8636-4bd0-94ae-b1348d5a89dc>" %}

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.5.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.