Core Web App

Have diagramming natively built-in instead of using embeds. Nearly every other cloud-based platform similar to this has a native diagramming app or a means of integrating a 3rd party diagramming web app like Draw.IO , Lucid Chart, MS Visio, etc. I see other requests specific to this so it's definitely something people can benefit from having.

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.

Implementing support for storing FIDO2 Passkeys in Hudu where they can be used through the web extension or similar to login to passkey enabled services. We have requirements for some clients to have FIDO2 or other phishing resistant authentication, but the only way we can do that now is through a separate password manager like Keeper or 1Password.

Please add the new IPAM and Rack management functionalities to the client portal as well.

It would be nice to be able to send the client a link where they could create a secure note to send back to you. (containing missing credentials or other sensitive information)

Will there be an option to have a selfhosted AI agent tool? to be integrated

Right now only admins can do this. We want to limit the number of admins, for obvious reasons, but maintaining portal assets is becoming tedious very quickly. It would be a great help if our engineers with editor role could also add assets to the portal when they create them.

Be able to change the colors for passwords so searching through multiple passwords ins easier

Having a Client/Company To-Do list at the home screen would be extremely helpful. Right now we use the Notes section and it works okay, but having a checklist/checkbox type form at the Company homepage would be useful for our Tech's to use.

In the customer 'External Sharing' view of an asset, their asset list only shows the the Hudu primary 'name' field. We should be able to earmark other fields that we include in our lists to the customers' view as well. Not all the same, only specific ones that we wish to display. In some assets we actually use the Hudu primary field as a drop down of category, then subsequent fields are the actual descriptive name. Other assets especially ones pulled from integrations are a real mess and we can't even expose it to an end customer. Example attached.