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.
Have a feature idea or feedback on how we can improve Hudu?
Track SPF/DMARC/DKIM activity in website version history
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.
Option for top toolbar in new KB article editor
With the new KB article editor, it would be nice to have some way to revert to having the toolbar at the top, similar to the old editor.
Markdown Text Editor
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 Progress
UniFi OS - Add optional description for API key
With the current credentials implementation, it's difficult to tell multiple sets of credentials apart. Please add an optional name or description field to each set so users can easily identify what each key is for.
Make the password search and company filter order the same in the Chrome extension and the ScreenConnect helper
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.
Portal Access Concerns
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.
Option to render emojis as native characters in the 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.
Preview KB article in both light and dark mode when editing
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
Include Photos and Attachments in Backups
In addition to additional backup destinations aside from S3 it would also be beneficial to include attachments and photos in the backups.
Full Hudu Tenant Backup - More options like direct export locally
Hi, Could we get backup options other than just S3 buckets? Export locally to a ZIP or SMB share? I know ITGlue had local export options. Thank you!
Halo Integration - Auto archive or delete inactive Halo assets
Create an option in the Halo integration to automatically archive or delete assets marked as “inactive”. This will simplify the clean up process within Hudu when asset statuses change in Halo.
Checkboxes in Processes to include an X or (Didn't Do) option
This may seem like a silly/simple thing, but it would be great to have two options when checking a box in a Process Run. The green tick to indicate that the task or subtask is completed, and a red X to indicate that the task or subtask is acknowledged but not completed. This would saves us having Process Runs stuck at 20 - 50 - 80% indicated incomplete Processes because the person completing the Run has an edge case where a specific Task or Subtask cannot be confirmed done. A green tick always indicates that task was done, which isn't how things always work. I appreciate that there's a "note" section under the Task, but that isn't as intuitive as a simple X. And I appreciate that Tasks could be worded around it, but that isn't a great solution either. If you agree, this might be a very simple and useful addition?
Unifi OS SSID
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
Add Windows Passkey Manager Support
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
Allow "Match on primary serial" to link to an asset layout field
Currently primary serial is defined by integration cards. Please allow an option to match to an existing asset layout field.
Add a countdown timer or progress bar for OTP code expiration
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.
Set Radar device requirements by device type
Device Requirements in Hudu Radar apply to every device, so customers with mixed networks can’t require host-only fields like Domain, Last login user, Disks, and CPUs for servers without also blocking switches and other network devices from syncing. Removing those fields for everything weakens the quality gate that keeps incomplete server and workstation records out of Hudu, leaving gaps techs rely on for troubleshooting, audits, and lifecycle planning. Setting requirements per device type would let each type be checked only against fields it can provide.
Archived Assets - Asset Type
It would be helpful if archived assets had a table field with the name of the asset type they had. It would make filtering through a bunch of archived assets much easier.
Support confidential OAuth clients (client ID and secret) for the Hudu MCP server
Hudu’s MCP server currently registers every OAuth client as a public client. Dynamic client registration returns a client_id only, with token_endpoint_auth_method set to none, and there is no place in Admin > AI > MCP to create or view a client ID and client secret. Let admins create a confidential OAuth client for the Hudu MCP server from Admin > AI > MCP. This would include: A generated client ID and client secret Support for client_secret_post and/or client_secret_basic at the token endpoint Per-client redirect URIs, for example https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect The ability to rotate or revoke the secret Use case: MSPs standardized on Microsoft 365 Copilot who want Hudu documentation available as a federated source alongside their other Microsoft data.