> 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.257.md). # 1.4.257 2025-12-14 ## What's Changed ### \[New Feature] Automatically send notifications when Assets are added to specific Folders HIVO now allows the setup of automated notifications via Email and In-app as soon as new Assets are uploaded to specific Folders. **🔹 Feature Details:** * **Flexible Configuration per Folder:** Allows users to customize notification settings for specific folders rather than applying a general setting to the entire system. * **Notification Recipients:** * Notifications are sent to specific Users or entire Groups that have been configured. * Mandatory Requirement: Only users possessing the **'Can View All Assets'** permission are eligible to receive these notifications. * **The settings are as follows:** Select the folder -> Click the down arrow -> Select **Folder Actions**
*** ### \[New Feature] Asset Naming Automation This update streamlines the asset naming process by removing manual triggers and introducing real-time pattern application across the platform. **🔹 Feature Details:** * **Automatic Pattern Application:** Removed the manual "Apply pattern" button. Naming patterns are now applied instantly to assets upon selection. * **Dynamic Re-naming Logic:** The system now automatically recalculates and updates asset names based on the following triggers: * **Pattern Swapping:** Renaming Assets on Upload * Sort Order Changes * **Upload Approval - Selection Updates**: Adding or removing assets from a selection (specifically in Upload Approval) will dynamically refresh the naming logic for the current active selection.
👉 See more about "[**Renaming Assets on Upload**](https://support.hivo.co/upload/renaming-assets-on-upload)" here. *** ### \[UI/UX Improvements] Fix filename break word in Library Grid view 🔹 **Update Details:** * Fixed an issue where filenames were being cut in half (line-breaking mid-word) in the asset grid. * Filenames will now wrap naturally or truncate correctly to ensure readability (e.g., "Lucia" will no longer be split into "Lu" and "cia" across two lines).
*** ### \[New Feature] Report - Expiring Consent Status/ Deletion History/ Collections Users can filter the report timeframe and export the filtered results directly to a CSV file. **🔹 Feature Details:** * **Expiring Consent Status:** Effectively track and manage the status of consent documents nearing their expiration date. The report includes comprehensive details for: Item, Expiry Status, Consent Status, Expiry Date, and Days to Expiry.
* **Deletion History:** Provides a comprehensive report to track and audit the history of deleted data across the system. * **Multi-Item Type Selection:** Supports filtering the report by specific item types, including: Assets, Collections, and Templates. * **Audit Information:** Each report entry clearly displays: Item Name, Deleted At (timestamp), and Deleted By (the user who performed the deletion).
* **Collections Action:** Report to monitor activities related to Collections, : * **New collection created:** Logged when a new collection is added. * **Collection edited:** Logged when the information or structure of a collection is modified. * **Collection deleted:** Logged when a collection is removed from the system. * **Collection shared:** Logged when access to a collection is granted to other users or groups.
*** ### \[New Feature] Editor - Add ability to Crop/Scale/Move/Rotate inner Image layer Users now have full control over image assets within fixed template boundaries. **🔹 Feature Details:** To start editing, just double - click on any image within your template. * **Crop & Scale:** Adjust the size and framing of the image to fit the design. * **Move & Rotate:** Precisely reposition or tilt the inner layer for perfect alignment. * **Quick-Save Hotkey:** Simply press the Enter key to exit image editing mode and instantly save the current visual state.
*** ### \[New Feature] Recognition - Add clear Recognition action & Person Recognition Re-indexing **🔹 Feature Details:** 1. **Clear Recognition" Action** Added a feature that allows users to delete all recognition data for a specific individual. * Once executed, the recognition status for this profile will switch to OFF. * The system will stop identifying this face based on the old underlying vector data.
2. **Person Recognition Re-indexing** If you want to reset and re-identify an individual as a completely new person, HIVO has added the **"Enable Recognition for New Assets"** option within the Edit Details section. * Once activated, the system will treat all **subsequent appearances as data for a new person.** * Users can conveniently access and toggle this option directly within the **Edit Details** of the Person profile.
👉 See more about **"**[**Action on Anonymous Faces**](https://support.hivo.co/recognition/anonymous-faces-in-recognition#action-on-anonymous-faces)**"** here. 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.4.257.md?ask=&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.