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

# 1.4.240

2025-06-16

## What's Changed

### **Search Feature Update: Natural Language Search and Match Score Sorting in HIVO Library**

We have launched a new **smart search feature using Natural Language Processing (NLP)**. This update enables users to search more easily and naturally — no need to remember exact keywords. Results are now smarter and more contextually relevant, helping users quickly find what they need. Additionally, users can **sort results by Match Score** for even more control.

🔹 **Update details:**

1. **Natural Language Search:**\
   Users can now enter search queries in a natural, conversational way, such as:\
   👉 *“Show all images that contain Jane Smith”*\
   The system will automatically analyze and interpret the context of the query to return more accurate and relevant results.
2. **Sort by Match Score:**\
   Users can sort search results based on the relevance or "match score" between the query and the asset content. This helps easily identify the most relevant results.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FnXVUvkVCbMKF3M87CT3a%2FScreen-Recording-2025-06-13-at-14.31.30.gif?alt=media&amp;token=77d3ec3c-5235-41c3-8479-355158fbf379" alt=""><figcaption></figcaption></figure>

#### **👉** Read more:[ Searching for Asset ](https://support.hivo.co/library/searching-for-assets)here.&#x20;

***

### **Run Governance Risk & Compliance Checks: Updated Comment Display per Page in Fullscreen Mode**

HIVO has improved how comments are displayed in fullscreen mode after running Governance Risk & Compliance Checks.

🔹 **Update Details:**

* Previously, when viewing an asset in fullscreen mode, comments were only shown for the first page (Page 1), regardless of the page being viewed.
* Now, the comment section will automatically update to match the page the user is currently viewing in fullscreen mode.

This allows users to follow and respond to comments on a page-by-page basis, improving accuracy and user experience.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FAnDJs1FrRJfonjolwZvg%2FScreen-Recording-2025-06-13-at-14.29.57.gif?alt=media&amp;token=9b976ad9-13dd-4af1-8ad2-883f9a773e29" alt=""><figcaption></figcaption></figure>

#### &#x20;**👉** Read more: [Risk and Compliance Settings ](https://support.hivo.co/client-profile/client-profile-settings/risk-and-compliance-settings)here.&#x20;

***

### Update Collection: Add Header Tags in Collections (*Applicable to selected clients*)

HIVO has introduced the **Header Tag** feature in Collections to support user groups who require clearer content categorization in the asset display interface.

🔹 **Update Details:**

* Allows adding **Header Tags** to divide content within a Collection into clearly defined groups.
* This update enhances **visual clarity** and makes it easier to navigate when presenting multiple assets within the same Collection.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Fd5kRwcqOjUufgFN1qaJm%2FScreen-Recording-2025-06-13-at-14.45.40.gif?alt=media&amp;token=7d163825-3132-4653-ae32-36e700719bd6" alt=""><figcaption></figcaption></figure>

#### &#x20;**👉** Read more: [Collection Detail Page ](https://support.hivo.co/collections/collection-detail-page)here.&#x20;


---

# 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.4.240.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.