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 log in removed the single click to sign in, and users must now enter their email each time to log in to the instance. Please offer an option to return the one click SSO sign in.
Currently, the MCP can read Related Items, but not modify. Please create tools to allow modification of Related Items.
Checkbox fields always show on an asset, even when they are not checked. On assets with many checkboxes, such as device roles or printer features, most of the page is taken up by items that do not apply. We would like an option on checkbox fields, or on the asset layout, to hide a checkbox when it is not checked, or to show only the checked items. This would make assets quicker to scan and would help teams that track lots of yes or no attributes.
If I search for something like a circuit reference for a fibre line, the search does not bring up any results. Why can’t the search all actually search ALL. As some context to this. If we get an email saying that there will be some maintenance work on a particular fibre line, we need to search to see which client that belongs to, so that we can notify them accordingly.
When comparing article versions, unchanged text in a changed line is shown on a light green background, and the actual edit is a slightly darker green. Those two greens are too similar, so the real change is hard to spot. Please highlight only the added/removed text in green/red, and leave the surrounding unchanged content uncolored (or with a much clearer contrast).
Currently, changes to admin settings aren’t recorded anywhere admins can review, so there’s no way to tell when a setting was changed or by whom. It would be helpful to have changes to admin settings recorded in the Activity Logs, including who made the change, when, and what changed. This would help teams track down the cause when something stops working, such as email delivery, and would support internal change tracking and audit requirements.
Currently, when an item is permanently deleted, there is no option to restore it directly from the UI. The recommended recovery process is to restore a backup to a separate instance and manually recreate or copy the required data. I completely understand the reasoning behind this approach, but I wonder if a simpler option could exist for day-to-day operational mistakes. Would it make sense to introduce a Deleted Items / Recycle Bin feature? For example: Deleted items would be retained for 30 days (or a configurable period). Admins could review and restore deleted records from the UI. After the retention period, items would be permanently removed. Activity logs and deletion details would remain available. In my experience, accidental deletions are much more likely than full disaster recovery scenarios. Having a safety net for restoring a single asset, password, article, website, or company record could save a lot of time and reduce the need to work with backup restores for relatively small incidents.
Currently it doesn’t appear an agent using the MCP can do anything in IPAM. This function would be very useful for day to day work and agent based automation workflows.
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.
We used to be able to resize an image right in the KB editor. What happened? Ability to resize and crop in editor is basically a necessity. Can we get this back?
Currently, there’s no way to see in Hudu whether an alert has fired, or whether its email or webhook delivery succeeded or failed. The “Test WebHook” option confirms the connection works, but it doesn’t show whether the scheduled alert actually ran. It would be helpful to have a delivery history for each alert, showing when it triggered, which records it included, and whether each email and webhook was delivered successfully or failed (along with the error). This would let admins confirm that alerts are working without waiting on the receiving system, troubleshoot missed alerts on their own, and catch delivery problems before an expiration slips through unnoticed.
When requesting a password via link, it would be nice if we could reveal the password before accepting or rejecting the write to the password in Hudu. Currently, you have to go to the revision history and copy the old password to roll it back if the provided password doesn’t meet criteria, which can only be viewed after accepting the change.
Microsoft 365 Copilot agents built with the Microsoft 365 Agents Toolkit can’t currently connect to Hudu’s MCP server. During setup, Microsoft requires the server to issue a client secret when the agent registers, and Hudu doesn’t. Please add support for this so Hudu MCP can be used directly in Microsoft 365 Copilot, without Copilot Studio.
Currently OpenAI is the only option for Sematic search but we use Claude. Please add Claude as an option to enable sematic search.
Can you possibly add the ability to upload an image to show an icon for applications in the list view for application assets?
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.
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.
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!