Please check existing posts to see if your feature request already exists.
🐛 If you’ve encountered a bug, please submit a ticket to the Hudu support team to ensure a quick response.
The new Huntress integration create identity objects using the email address rather than attempting to match an existing object that contains the email address. Since we migrated from IT Glue our roughly 20k identities are created using the actual name of the user. Different matching options would make this more usable.
The new Huntress integration allows syncing of agents, but it assumes all agents will the same asset type in Hudu. We currently distinguish between user endpoint and servers. Is it possible to allow more elaborate mapping?
We use Hudu to build customer audits. For each topic (e.g. Broadband) we need two asset layouts: one for the technical details, and a second “audit” layout holding the RAG rating, who updated it, the date and our recommendations. That doubles the layouts we set up and maintain, and the rating isn’t visible on the page where the assets live. The idea would be to let a layout hold one overall assessment per customer: Rating (admin-defined labels and colours) Reviewed by and date (automatic) Summary and recommendation Show it in a banner above the asset list, and include it in the layout’s export and accessible via the API. We feel this would be useful to anyone doing audits, security reviews or client QBRs. Example Mockups:
Secure notes currently produce a link that the technician has to copy and deliver through another channel. We’d like a “save and send” option that lets the technician enter a recipient and have Hudu deliver the link directly. Optional SMS delivery through a third-party SMS provider would be a further improvement. This would let MSPs handle secure one-off sharing entirely in Hudu instead of relying on a separate tool.
Currently, changes to SPF, DMARC, and DKIM records are not captured in the version history for websites. Reasoning: some third parties manage domains for our customers, and mistakes sometimes happen during record transfers, resulting in records being deleted. Having the ability to see past records when changes occur would help identify what was lost or changed and when.
I have some concerns with the User Portal changes in v2.47, specifically around password visibility and permissions. First, passwords stored in a client's root folder appear to be accessible to portal users by default. From a security standpoint, I'd prefer a default-deny approach that follows the principle of least privilege. Access should be explicitly granted rather than requiring administrators to take additional steps to restrict it. This is particularly concerning for existing passwords that may have been created without any expectation of being accessible through the User Portal. We shouldn't have to reorganize credentials into subfolders or modify individual records simply to maintain their existing level of access. Second, relying primarily on folder-based permissions creates unnecessary complexity. For example, if John needs access to Password 1 and Password 2, but Janet only needs Password 2, we now have to create separate folders to accommodate those permissions. Since a password can only reside in one folder, this also forces us to organize credentials around access requirements rather than their logical purpose. I understand the goal was to move away from the previous portal's permission model, and I can appreciate the benefits of folder-based permissions for managing access in bulk. However, I think there should still be an option to restrict access by default and grant permissions at the individual password level. Ultimately, I'd like to see folder-based permissions and individual record sharing coexist. That would provide flexibility without compromising least privilege or creating unnecessary administrative overhead.
Individual passwords can currently only be restricted by blocking groups, through More Options and Change Permissions. There is no way to allow a password to a specific group and hide it from everyone else. The only allow list for passwords is at the password folder level, where a folder can be set to Selected Groups. On an individual password, under More Options and Change Permissions, add the option to restrict the password to selected groups (an allow list), similar to Who can view this folder on password folders. Groups not selected would not see the password. Admins and Super Admins would still always have access. This should apply to portal users as well as internal users.
Add a markdown editor option so users can write and edit content in markdown instead of pasting/importing/export with the current text editor.
In the new Notion-style editor, emojis are rendered as image files from an external emoji set instead of as native Unicode characters. Emojis typed or inserted into an article are converted to images, and users can’t turn this off. This is a change from the previous editor, and some users find the image-based emojis look lower quality than the native emojis they’re used to. We’d like emojis to render as native Unicode characters, either as the default or through an account-level or user-level setting. Existing articles that already contain image-based emojis would ideally display natively as well under that option.
Currently primary serial is defined by integration cards. Please allow an option to match to an existing asset layout field.
Requesting SSID sync support, specifically: - Sync each SSID per site into a chosen asset layout, with an Asset Layouts option similar to the existing device categories - Include SSID name, security type, linked network/VLAN, band, enabled status, and guest flag - Optionally store the WiFi passphrase as a linked Hudu Password - Relate each SSID to its network in IPAM and to the access points broadcasting it
It would be great if you could add a light/dark mode switch when editing KBs so that you can easily check how the colors look on both before publishing. Otherwise you have to keep 2 windows open - one for each mode
Just worst case scenario could there be a limited FULL Admin so in case Microsoft SSO or other platforms are down for an extended period that admin can revoke SSO requirement during that period of time. Ideally it’s never an issue but it’s good to have it in the tool belt!
The Chrome extension and the ScreenConnect helper put the password search and the company filter in opposite order: ScreenConnect helper: “Search all passwords” is on top, “Search companies” is below it. Chrome extension: the company filter (“All Companies”) is on top, “Search passwords” is below it. Our techs use both tools all day, often switching between them during the same ticket. Because the fields are flipped, we keep typing into the wrong box: a password search ends up in the company filter, or a company name ends up in the password search. Request: use the same layout in both extensions, so the password search and the company filter are always in the same position. Either order is fine, as long as it’s consistent.
Allow Hudu assets to sync into Halo via the integration, similar to how the KB article sync works.
We would like two improvements to the website overview: Automatic retrieval of hosting data Customizable columns in the overview 1. Automatic retrieval of hosting data Hudu would automatically detect and store hosting details for each monitored website, so this information doesn’t have to be looked up and entered manually. Useful data points include: Hosting provider (for example, GoDaddy, WP Engine, AWS, Azure, Cloudflare) IP address the domain resolves to Name servers and DNS provider Registrar, if available Location of where the website is hosted. The data should refresh on a schedule so it stays accurate when a user changes hosts. 2. Customizable columns in the overview The overview currently shows data that can not be manually modified. We would like a notes page, or the ability to add custom fields to a website entry..
The Passkey support in Hudu lacks the ability to integrate with Windows. It makes it impossible to login with a Passkey stored in Hudu when using the Exchange-Online PowerShell module as one example. Here is a link to Microsoft's documentation for this feature: https://learn.microsoft.com/en-us/windows/apps/develop/security/third-party
It would be helpful to have a countdown timer or progress bar indicating how long remains before an OTP code refreshes. Ideally this would be visible whether the code is revealed or masked, though support for either state alone would still be valuable. The goal is to gauge remaining validity without needing to view the actual digits.
today you are pulling in all the networks to IPAM through the integration but not adding the VLAN to it. Might be related to this UniFi network config add vlan to networks IPAM overview - Hudu but thats for the old integration i believe. Also a side note, saw that “UDM Pro Max” was tagged as a “switching” but that might be UI API issue, so it got added to the switches instead of gateways.