Skip to main content

Have a feature idea or feedback on how we can improve Hudu?

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.

Enable one-click SSO sign in

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.

Core Web App25 days ago
8

Allow MCP to modify Related Items

Currently, the MCP can read Related Items, but not modify. Please create tools to allow modification of Related Items.

Core Web App12 days ago
1

Option to hide unchecked checkboxes on an asset

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.

Core Web App12 days ago

Search All Does not Search All Fields

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.

Core Web App8 days ago

Huntress Integration Identity Matching

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.

Integrations27 days ago
3

Allow MCP to access expirations

Create tools for the MCP server to read and write expiration data.

Core Web App12 days ago
1

Huntress Integration Agent Sync

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?

Integrations27 days ago
2

Clearer change highlighting in Compare Differences

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).

Core Web App14 days ago

Logging for Changes to Admin Settings

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.

Core Web App11 days ago

Deleted Items - Recycle Bin Feature

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.

Core Web App26 days ago

Allow companies to be searched by company summary details

Searching companies by address, phone or fax number, or website should return that company in the results.

Core Web App4 days ago

Asset Archive Status

We are noticing that if we archive an asset that we keep in custom asset such as a network device, it remains in the Racks layout. The scenario is you have a switch that is retired, you document that retirement per your procedures and then set that device to archive. In the real world, my tech has removed that switch for recycling. Should that not automatically remove it from the rack and other linked references? When you place the asset in the rack, sure would be nice if that asset had a magic link to the rack object. It doesn’t today, not by default or automagically and there is no asset magic link option to select a rack. Hudu’s power comes from our ability to link assets and objects per their logical relationships.

Core Web App4 days ago

KB Magic Link to Process

KB’s do not have a magic link for processes, you can not link a relationship natively from within the KB. Alternative, if you make the link to the KB from the process it does present that relationship. This needs to be harmonized with the similar functions of Hudu everywhere else.

Core Web App4 days ago

Restrict API keys with password access to specific password folders (so a breached integration can’t expose every password).

Hi Hudu team, Integrations like CyberQP QuickPass password rotation tools need API access to read and update passwords in Hudu. Today, once an API key is given the “view passwords” permission, it gets full access to all passwords, including viewing, editing, and deleting. A key can be limited to a company, but not beyond that. If an integration vendor is breached, an attacker could reach every password in the scope of that key. Why now: Last week’s compromise of ConnectWise’s cloud backup gave attackers access to the Microsoft tenants connected to it. It made us look at every vendor with access to our data, and a vendor with broad password access in Hudu is one of our biggest exposures. Request: add a folder limit to API keys, the same way we can limit them to a company today. An admin could restrict a key to: A folder belonging to one specific company, or A global folder, giving the key access to that folder across all companies The key would only be able to access passwords inside the folders it’s been granted. Also requested: let admins edit existing API keys, including permissions, company and folder limits, and IP restrictions. Today, tightening a key (such as adding an IP restriction or updating an IP) means deleting it and creating a new one, which also means reconfiguring the integration. Also helpful: separate view, create, edit, and delete permissions for each availble asset, including passwords only with no asset access instead of one “view passwords” toggle that grants everything. This would let MSPs use password automation without making every vendor a single point of failure. Thank you!

API19 days ago

Add IPAM to Hudu MCP

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.

Core Web App25 days ago
2AI, MCP, CLI

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.

Core Web App1 month ago
5

ConnectWise RMM (Asio) - Sync additional device details

Are there plans and a roadmap to bring in more device details from ConnectWise RMM (Asio)? The current integration syncs companies, sites as locations, and devices, but the device data is limited. To fill the gap, I currently run a PowerShell script that pulls data from the ConnectWise RMM API and pushes it into Hudu. I would like the native integration to handle this so I can retire the script. Device details I would like synced: Hardware: manufacturer, model, serial number, CPU, memory, and storage. Operating system: OS name, version, and build. Network: IP addresses, MAC addresses, and domain. Status: last check-in, online status, and last logged-in user. Patch status: available and installed patches. Installed software inventory. These details are available through the ConnectWise Platform API: GET /api/platform/v1/device/endpoints GET /api/platform/v1/device/endpoints/{endpoint_id} GET /api/platform/v1/patching/{endpoint_id}/patches Having this data synced natively would keep our device documentation accurate without custom scripting, bring the ConnectWise RMM integration in line with other RMM integrations in Hudu, and make the connected fields far more useful.

Integrations8 days ago
1

KBs resizing inline graphic

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?

Core Web App25 days ago
1

Alert History or Logs

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.

Core Web App11 days ago

Allow hiding asset layout fields without deleting data, and sync make and model as separate fields from CW RMM

The ConnectWise RMM integration currently populates a combined “Make & Model” field. It would be helpful to split this into two separate fields, Make and Model, for cleaner organization and reporting. During that transition, there should be an option to hide the existing combined field while temporarily retaining its data, making it easy to compare and identify which assets aren’t being populated through CW RMM. This would require support for hiding asset layout fields without data loss, along with the ability for the CW RMM integration to sync make and model to individual fields.

Integrations12 days ago