# 1.5.13

## What's Changed

### **\[Enhancements]** Support Ticket Notifications

We’ve introduced a new notification system to keep all involved users updated on support ticket activities in real time.

**🔹 What's New**

* Users will now receive notifications when they are involved in a support ticket and there is: **A new comment, A reply to their comment, A mention (@mention)**
* How to configure notifications:
  * Notifications will be sent via configured channels: **In-app, Email, or both.**
  * Select events to receive notifications: New comments, Replies, Mentions.
  * Enable/Disable each type of notification as needed.
* Admins can configure settings for all users via the following path: Client Profile -> Settings -> [**Global Notification Settings**](https://support.hivo.co/client-profile/client-profile-settings/system-and-integration/global-notification-settings)

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

* Or for a Specific User Group: Client Profile -> Open Groups Settings -> [**Notification Settings for Group**](https://support.hivo.co/client-profile/groups/notification-settings-for-group)**.**

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

***

### **\[Enhancements]** Assign Entities to Support Tickets

We’ve enhanced the support ticket workflow by introducing automatic assignment to ensure every new ticket has a clear owner from the moment it is created. This ensures all incoming tickets are centrally tracked and managed immediately

**🔹 What's New**

When a new support ticket is created:

* The ticket is automatically assigned to the default support account: HIVO\_support\_client.&#x20;
* The accounts HIVO\_support\_client need to be delegated rights to view/ edit/resolve the ticket if they are not the admin.&#x20;

If needed, Client Admins can later re-assign the ticket to another admin for further handling or escalation.

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

***

### \[Improvements] Improved Comment Filtering for PDF Documents

We've improved how comments are displayed in PDF documents to ensure users only see comments relevant to the page they're currently viewing. This makes it easier to track and address feedback for each page.

**🔹 What's New**

* Previously, Compliance comments (e.g. spelling, legal, risk) were filtered by the current page. Normal comments were displayed across all pages, regardless of the page being viewed
* Now, All comment types — including both compliance and normal comments — are filtered by the current page

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

***

### \[Improvements] Simplified “Edit Related People” in Consent Workflow

We’ve streamlined the **Edit Consent** workflow to reduce friction and eliminate the risk of losing changes when assigning related people to assets.

**🔹 What's New**

**Before:**

* Users had to go through multiple steps to assign related people
* Required manually clicking **“Save Related People”** for each action
* Closing the dialog without saving resulted in **lost data**

**Now:**

* The **manual “Save Related People” step has been removed**
* Changes are **automatically retained** when you close the dialog
* The workflow is more intuitive and requires fewer interactions

**🔹 Updated Workflow below:**&#x20;

1. Select Assets&#x20;
2. Go to **Actions → Edit Consent**
3. Click **Related People** -> Assign people directly
4. Click **Close** -> Click **Submit**

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

***

#### **\[Enhancements]** Consent Approval – Add Consent Source Tracking

We’ve enhanced consent management by introducing **Consent Source** tracking, giving users better visibility into where each consent was created and improving traceability across workflows.

**🔹 What's New**

A new **Source** field has been added to consents to identify how the consent was created.

Available source values include:

* **Library** – created directly from the asset library
* **Manual** – created manually by users
* **Consent Face Request** – created from a Consent Face Request workflow

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

***

### **\[Enhancements]** Add Images to Comments on Asset Detail Page

We’ve enhanced the [commenting experience on the Asset ](https://support.hivo.co/assets/commenting-on-assets)Detail page by allowing users to attach images directly within comments.

**🔹 What's New**

Users can now add images when creating comments on an asset detail page using two sources:

* **Upload from computer**
* **Select from the asset library**

This makes it easier to provide visual feedback, references, and clearer communication during review and collaboration.

<figure><img src="/files/3MWNDnHLelyhWHXNU83E" alt=""><figcaption></figcaption></figure>

If you have any questions, don't hesitate to ask, we're always here to help!


---

# Agent Instructions: 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:

```
GET https://support.hivo.co/changelog/1.5.13.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.