For the complete documentation index, see llms.txt. This page is also available as Markdown.
1.6.1
2026-07-17
What's Changed
[New Feature] Custom FAQ for Each Client
HIVO introduces the Custom FAQ feature, allowing each organization to build and manage its own set of frequently asked questions. FAQ data is segregated and only visible to users within the same organization.
Client Admin: Create, edit, delete, and reorder FAQ items.
Regular Users: Search and view FAQs in read-only mode.
This feature enables clients to proactively provide support content, quickly resolve common queries.
👉 How to enable/disable: This is a custom feature. Please contact the HIVO team for assistance.
[New Feature] Color Palette Management
You can now view and edit color table mappings, with custom color tables automatically saved when creating new templates. This feature controls color quality right at the export stage, ensuring a seamless workflow from Design to Printing without the risk of color mismatch.
🔹 What’s New?
Automatic Template Saving: Color palette settings are now automatically preserved and applied when saved to new templates.
Color Mapping on Export: Easily map RGB colors to CMYK values when exporting PDFs in CMYK mode.
🔹 How to Use (Explore the product tour below)
Navigate to Detail Template -> Click the Edit button.
Scroll down to the Colour Palette section.
Configure your color settings:
Enter your mappings under Map RGB colours to CMYK values when exporting PDFs in CMYK mode.
Click Add Entry to add a new color mapping rule.
Save your changes.
[Improvement] Allow Multiple Consent Submissions for One Person
Users can now submit multiple consent forms/records for the same recognized person without encountering submission errors.
🔹 What’s New?
Previous, attempting to submit a second consent form for a person who already submitted one resulted in a "consent already submitted for detected person [400]".
Current, individuals can now scan and submit the same QR code multiple times. All submissions will be consolidated under their original profile without creating duplicate entities or triggering errors.
