Core Web App

I know I heard this is on the roadmap, I'm just putting it out there for discussion amongst users in order to make this the best on the market! I would love to see asset types mapped to configuration types and automatic 2 way sync. It would be great if Hudu could also create a URL field within the configuration of the PSA that links to the Hudu URL and/or a section/pod (if possible) that has links to the related configs alongside passwords. (I'm thinking of a Hudu section on a config that is similar to the Connectwise part on the bottom of a linked object on Hudu...)

2fa is supported with rolling codes but hardware tokens should be supported as well.

It would be nice to have the Description field added as a column to the list. For IP addresses that dont have an assigned device the Description field would help to identify what the IP address is associated with

Additional option under Network Management to have patch panel port descriptions and labeling added.

Issue: We would like to request an enhancement for the PDF viewer in Hudu. Currently, the PDF viewport is limited in size, making it difficult to view larger documents with ease. Expanding the PDF viewport would provide a larger, more readable viewing area for users. Suggested Improvement: Increase the size of the PDF viewer to utilize more screen space. Implement a "full-screen" mode for PDF viewing to allow users to maximize the viewport for better readability. Use Case: This enhancement will improve user experience when working with larger PDF documents, making them more accessible and easier to read without needing to constantly zoom or scroll. Benefits: Improved usability for viewing long or complex PDF articles. More efficient workflows for users interacting with detailed PDF documentation.

Sometimes we have repeatable tasks that we document our progress by using "Processes". If there are a lot of tasks it can be a bit of a PITA to unclick each one and reset the process completion back to 0%. I'd love to have a "reset process" button and then a confirmation dialog box to confirm thats what's wanted before its done. Thanks!

When importing IP addresses, allow Hudu to automatically relate them to existing device assets based on matching IP or hostname, instead of requiring manual assignment for each one.

It would be nice to ship logs to Huntress SIEM for analysis / archiving.

I note that in the documentation we can can use a custom list for network statuses but not for IP statuses. https://support.hudu.com/hc/en-us/articles/20718639574423-IP-Address-Management-IPAM I'd like the ability to use a list for IP statuses as well. I appreciate I might be a bit dim but I can see room for error in the existing terms: -DHCP - Is it served by DHCP or is it dynamic (the IP could change and to which point is there value in documenting it in IPAM?) -Reserved - Does this mean it's reserved in DHCP but deployed dynamically?

I would like to request a new field type for Asset Layouts: Rich Text (Template). This field would allow default content to be defined at the layout level and automatically appear inside every new asset created from that layout. Why This Is Needed: MSPs rely heavily on standardized processes and reusable instructions. Some sections of an asset layout require consistent guidance, reference material, or step-by-step instructions every time a technician documents a new integration. Examples include: Examples of sections within an Asset Layout that need reusable default content: OAuth2 configuration reference blocks (grant types, token URLs, auth URLs, scope formats) Standard API parameter definitions (client ID vs. tenant ID vs. app ID vs. secret; expected formats; naming conventions) Common integration prerequisites (required permissions, admin consent steps, API toggles, IPs to whitelist) Reusable code snippets or request examples (API POST/GET templates, Graph calls, curl commands, JSON bodies) Vendor-specific “gotchas” that every integration requires (Acronis: need tenant UUID; Keeper: need public/private key pair; Proofpoint: region selection, etc.) Version-specific notes for recurring integrations (e.g., “For all Graph application-permissions integrations, always use https://graph.microsoft.com/.default” ) Standardized screenshot placeholders (“Insert screenshot of consent page here”) Internal documentation standards (required fields, expiration policy, required test validation steps) “How to complete this section” instructions for junior staff Without a field that supports default templated content, technicians must manually paste the same guidance into every new asset. Across many clients and integrations, this leads to: Inconsistent documentation Higher risk of missing critical steps Repetitive manual work for every new asset More training and overhead for new team members Requested Functionality: A new field type—Rich Text (Template)—that allows: Default content stored in the Rich Text field in the Asset Layout itself Support for formatted Rich Text (headings, lists, spacing, links, etc.) Automatic insertion of this content into every new asset created from the layout Ability for technicians to modify the field after the asset is created (like normal Rich Text) Benefits: These are reusable technical instructions tied directly to the Asset Layout Stronger documentation standardization Faster asset creation and reduced repetitive work Lower risk of mistakes in complex configs (OAuth2, SSO, vendor APIs, security baselines) Better onboarding and self-guidance for technicians Asset Layouts become true templates, not just field definitions This enhancement would significantly improve workflow efficiency for MSPs and any teams using Hudu for standardized technical documentation. Thank you!