> 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.236.md).
# 1.4.236
## What's Changed
### **Notification Settings Sync Enhancements for User Groups**
In this update, the system has been improved to enhance the synchronization of **notification settings** between **User Groups** and **their members.** Newly **added users (either manually or via SSO)** will now automatically inherit the correct notification settings from their assigned group.
***
### **Update to Asset storage process when creating a Brief: Change in Handling Attached Files**
Previously, when users attached assets during the process of creating a Brief, the system would automatically upload and store those assets in the HIVO library—even if the Brief was not successfully submitted.
However, in practice, there were cases where users canceled or did not complete the Brief creation process, resulting in unrelated or unused assets being stored unnecessarily in the library.
👉 **New Update:**
* Assets attached during the Brief creation process will now **only be saved to the library if the Brief is successfully submitted**.
* While drafting, files will be temporarily held and **only officially stored once the Brief is completed**.
This update helps **avoid unnecessary storage** of unapproved or unused content, keeping the asset library more organized and relevant.
***
### **Asset Duplication Update: Add Suffix when Duplicating Assets**
When users use the **Duplicate Asset** feature, the system will now automatically:
* Add the suffix **“-1”** to the name of the first duplicated asset
* Increment the suffix number for each subsequent duplication (e.g., **“-2”, “-3”,...**) from the same original asset, example:
* Original: banner.jpg
* First duplicate: banner-1.jpg
This update will help users easily distinguish between duplicate versions, preventing unwanted duplicate filenames.
---
# 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.236.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.