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

# 1.5.14

## What's Changed

### \[Improvement] Enhanced Image Naming Validation

Image Readiness now includes **Naming Convention** validation, helping teams ensure uploaded assets follow consistent file naming standards before they are approved.

**🔹 What's New**

* Validate image file names against your organization's naming conventions as part of the Image Readiness workflow.
* Ensure files include required identifiers, such as **Product ID** or **SKU**, to support consistent asset organization and easier searchability.
* Support flexible validation rules, allowing you to enforce required prefixes, suffixes, or keywords based on your naming standards.

<figure><img src="/files/SseTB33qDAk153n5sKWW" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UIvkAMrdtLtpkcfOQq42" alt=""><figcaption></figcaption></figure>

***

### \[Improvement] Enhanced Upload Destination Selection

We've improved the upload experience to help users save assets in the correct location from the start, while giving administrators greater control over where assets can be uploaded.

#### 1. Upload Assets Directly from Approval Checklists and the Editor

**🔹 Before**

* Adding an asset immediately opened your device's file browser.
* In [**Approval Checklists**,](https://support.hivo.co/tasks/task-detail-page#task-checklist) users had to open the checklist item in edit mode before attaching an asset.
* When selecting **Choose Other Source** in the Editor, there was no opportunity to choose where the uploaded asset would be stored.

**🔹 What's New**

* Before selecting a file, you'll first choose the destination folder for the uploaded asset.
* Upload assets directly from **Approval Checklists** without leaving the checklist or opening the item editor.

<figure><img src="/files/6mO8AUEtlWc0w8m14m38" alt=""><figcaption></figcaption></figure>

* When using **Choose Other Source** in the Editor, you can select the destination folder before uploading, making it easier to keep assets organized.

<figure><img src="/files/UgzzeAwNSk2xQ41S0ML3" alt=""><figcaption></figcaption></figure>

#### 2. More Control Over Asset Upload Destinations

Admins can now better manage where uploaded assets are stored for different user groups.

**🔹 Before**

* Users could upload assets without being prompted to select a destination folder, even when organizations wanted uploads to be stored in specific locations.

**🔹 What's New**

* Admins can configure whether users in specific user groups are required to select a destination folder when uploading assets.
* If a destination folder is required, users must choose a folder before they can continue uploading.
* Admins can also configure a **default destination folder**. If users do not change the selected folder, assets will automatically be uploaded to the preconfigured location.

<figure><img src="/files/HhB1d2k28pAY96w3UFGt" alt=""><figcaption></figcaption></figure>

***

## \[Improvement] Greater Control Over Automated Tags

HIVO has enhanced **Tag Settings** to give Admins more control over how [**Automated Tags**](https://support.hivo.co/client-profile/client-profile-settings/asset-and-metadata-management/tag-settings#id-3.-automated-tagging-control) are applied, helping improve tagging accuracy and reduce unwanted results.

#### 1. Minimum Confidence for Tag Recognition

**🔹 Before**

* Automated Tags were applied using the system's default confidence threshold.

**🔹 What's New**

* Set a custom minimum confidence threshold for **Automated Tags**. Only tags that meet or exceed the specified confidence level will be applied automatically.
* Enter **0** to continue using the default threshold of **70%**.

<figure><img src="/files/CUu9BabeklZVXJF0S6EH" alt=""><figcaption></figcaption></figure>

#### 2. Blacklisted Tags Moved to Tag Settings

**🔹 Before**

* **Blacklisted Tags** were managed in a separate settings section.

**🔹 What's New**

* **Blacklisted Tags** are now managed directly within **Tag Settings**, alongside other Automated Tag controls option that allow Admins to manage excluded tags from a single centralized location for a simpler configuration experience.

<figure><img src="/files/4ATDjJGhF3TpODLWlGHu" alt=""><figcaption></figcaption></figure>

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 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/changelog/1.5.14.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.