Core Web App

I'm missing an DHCP Scope entry in the new Network Management tool. When adding a network I would like to add the DHCP scope so they appear in the list as DHCP assaigned. It wouls also be great if a DHCP line could be changed to DHCP Fixed (or simular) and assignig a device in that case.

In the Assets Ninja pulls over I´m missing the Warranty field, the integration pulls over all the other data so filling that in manually afterwards is quite the hassle. Ninja pulls the warranty data from the vendor automatically so bringing it over in Hudu as an expiration date would be very nice.

I would be nice to be able to add files to a process, just like adding files to a KB.

We have some passwords that Super Admins only need to have access to but we cannot allow Admins to have access to - since passwords are only controlled by groups and Admins can't be part of Groups we have a major issue with this - we need more granular control of who can see certain passwords

Currently, Meraki device tags do not sync into Hudu. It would be helpful if tags assigned to devices in Meraki could be included during the sync so they are available within Hudu for organization and filtering purposes.

We generate unique credentials for appliances and devices. Sometimes our clients request these credentials. The ability to create a strong, unique password and have it generate a link to retrieve the password and have it expire after viewing would be nice.

Add the ability to merge multiple asset layouts and their assets into a single asset layout within Hudu.

Currently, there is no option to export the user list. It must be copied and pasted manually (and not cleanly either) in order to review for audit purposes. It would be best to have a CSV or XLSX export of the users and their roles.

Currently, secure notes can either expire after a set time or after a single view. I suggest expanding the "Expire after 1st view" checkbox into a configurable dropdown or input field. This would allow users to set a specific threshold (e.g., "Expire after X views"). This functionality is essential for sharing sensitive information with a small group of stakeholders while ensuring the link remains secure once everyone has accessed it.

Hi Hudu team, We’d like to request an improvement to how credentials can be associated with assets. Problem / current limitation Today, credentials can be stored in Hudu, but it’s difficult to structure them directly on an asset in a way that explains what each credential is used for on that specific device/service. In practice, we often have multiple logins tied to the same asset (local admin, iLO/iDRAC, application login, VPN profile, service account, etc.), and it becomes unclear which password belongs to which purpose. Requested feature Add a field type in Asset Layouts that lets us select/reference an existing Credential (similar to a relationship picker), and optionally provide a short usage/description per referenced credential. Example: • Field label: “Credentials” • Inside the asset, we can add one or more credential references: • Credential: “Server01 - Local Admin” Usage: “Local admin login for maintenance” • Credential: “Server01 - iLO” Usage: “Out-of-band management” • Credential: “App Service Account” Usage: “Used by the scheduled task / service” Expected behavior / UX • In an asset layout, admins can add a “Credential Reference” field (single-select or multi-select). • When editing an asset, users can pick one or more existing credentials from Hudu. • Each picked credential can have an optional text description (purpose/where it’s used). • The asset view should display these references as clickable links to the credential item (with permission checks applied as normal). Why this matters • Reduces guesswork and mistakes when multiple credentials exist for a single asset • Makes onboarding and handovers easier (clear purpose per credential) • Keeps credentials centralized while still making them actionable on the asset Acceptance criteria (suggested) • New “Credential Reference” field type available in Asset Layouts • Supports single or multiple credential references • Optional per-reference description field • Clickable link from asset to credential (respecting existing credential permissions) If helpful, we can share real examples of how we structure assets and credentials today.