> 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.237.md).
# 1.4.237
2025-06-05
## What's Changed
### **Add Metadata for Collections**
In this update, the system introduces the **Collection Metadata** feature, allowing users to add metadata to collections via the **Collection Settings**.
* These metadata values will appear in the **Collection dropdown filter**, enabling users to quickly search and filter collections based on relevant criteria.
***
### **Add Permission and SKU (Product IDs) fields to Upload Approvals**
In the upload approval process, approvers can now:
* Assign **permissions** to assets directly during the review process
* Enter **SKU information** (product IDs) to improve product-level asset management
***
### **Add SKU (Product IDs) field to Upload Link**
When creating an Upload Link, **uploaders or external users** can now easily assign assets to existing **SKUs/Product IDs** that have been predefined by Admins or users with the **"Edit Product"** permission.\
This enhancement makes it easier and more accurate to categorize and manage uploaded content.
⚠️ **User Right Required:** User must have the ***“***Can create/update/delete Upload Links ***”*** permission to create Upload link.
---
# 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.4.237.md?ask=&goal=
```
`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.
.png?alt=media&token=4317fd7d-923c-4044-b17e-08f2291dfaa2)
.png?alt=media&token=9d5e5f74-2744-4fa7-97cb-a2e9c212c7f5)
.png?alt=media&token=4a23328e-dbe2-4afe-9c1e-a110c96d54b3)
.png?alt=media&token=b02cba8b-551b-4e6f-b630-44c1e92a3cbe)