Core Web App

It would be a great benefit to be able to sync the Hudu Global KB to Halo's Knowledgebase. Halo has a KB search when entering in a ticket and since we don't have our KB in Halo we would need a sync to allow the articles to be created/updated in Halo when entered into Hudu.

It would be great to have an unpaid, duplicate version of a user profile for testing different roles and groups. Alternatively, this could function as a temporary change to your current user account that can be quickly reverted, either immediately or after a set amount of time. This would save users from needing to pay for another license to test different user roles or groups in their Hudu instance.

Is it possible to check on the service tag of a system and find out when the warranty expires? Would be nice if this populated automatically like domain information does so we can get notified when a server is running out of support.

Would like the ability to store & edit documents such as Word, Excel, & Visio drawings from within Hudu.

Currently, expiration emails are received with the expirations sorted in a random order. It would be alert emails were sorted by the expiration date.

Currently SSL certificates can only be tracked if they are attached to a Live website. Would be nice to also be able to import a certificate used for other purposes (i.e.. VPN Certs, Internal Sites, Code Signing Certs, etc..)

Portal update to include any newly added information under the company external portal. On the external portal, new devices, documents, etc. that are added to the company do not automatically get shared to the portal . Can you add a check box to enable all newly imported Assets, Share websites, Share links, shared Passwords, Share article folders to be included if you check the box to allow this ?

Would be great if we had the ability to sticky documents within a folder so they appear at the top, as well as be able to sort them, similar to what you see on forums. This way for certain systems, there's a "Setup" or "READ THIS FIRST" sort of document that can sit at the top so that any important details are given first and foremost, rather than just having the documents sorted in alphabetical order. Additionally, the option to highlight them with a particular color, as you do with callouts within a document for example, would be cool too. This way a newbie can immediately go to the documentation, take note of the highlighted/stickied documents, and follow them accordingly. This would also be great for project teams who have upgraded systems so that the updated documentation gets more visibility. As it stands right now, best we can do is append document titles with a numerical value like "1 Read this first!" which leaves a lot to be desired. Thanks!

It would be good to be able bulk upload photos then be able to; bulk rename Basic editing of photos, crop, rotate etc Assign them to an Asset from the photo gallery add tags/categories rather than having to rename. have folders for photos. Show and use meta data from photos such GPS, data and time etc Eg show all photos at that location or taken on that date.

In large MSP environments, asset templates often contain a very high number of custom fields to cover all possible documentation needs. While this flexibility is essential, it also creates a usability problem in Hudu’s asset view: When a section heading (sub-header) contains only empty fields, the fields themselves are hidden as expected — but the section title still remains visible. This results in long pages filled with unused section headers, forcing technicians to scroll unnecessarily to locate the relevant information. Requested improvement We’d like to see Hudu automatically hide entire section headers (and their spacing) when all fields inside that section are empty or have no data to display. For example: • If the section “Network Interfaces” has no filled fields → the section title should be hidden entirely. • If at least one field under a section contains data → the section title and that field group should be shown normally. Optional enhancement • Admins could toggle this behavior globally or per template (e.g. “Hide empty sections by default”). • A small indicator could optionally be shown in edit mode to make it clear that hidden sections exist. Benefits • Cleaner, more focused asset views. • Faster access to relevant data without scrolling through empty sections. • Dramatically improved readability for templates with dozens or hundreds of potential fields. In short, we’re requesting that empty section headers in asset views be automatically hidden when no fields under them contain data — making complex asset layouts much more efficient and user-friendly.