1.5.13
2026-04-21
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
Or for a Specific User Group: Client Profile -> Open Groups Settings -> Notification Settings for Group.
[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.
The accounts HIVO_support_client need to be delegated rights to view/ edit/resolve the ticket if they are not the admin.
If needed, Client Admins can later re-assign the ticket to another admin for further handling or escalation.
[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
[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:
Select Assets
Go to Actions → Edit Consent
Click Related People -> Assign people directly
Click Close -> Click Submit
[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
[Enhancements] Add Images to Comments on Asset Detail Page
We’ve enhanced the commenting experience on the Asset 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.
If you have any questions, don't hesitate to ask, we're always here to help!
Last updated