Core Web App

Portal update to include any newly added information under the company external portal. On the external portal, new devices, documents, etc. that are added to the company do not automatically get shared to the portal . Can you add a check box to enable all newly imported Assets, Share websites, Share links, shared Passwords, Share article folders to be included if you check the box to allow this ?

Please add the ability to add devices to a rack in descending order as shown in the example screenshot. Currently, if you try to add a device with a starting unit higher than the end unit it returns a "Create Failed" error.

Would be great if we had the ability to sticky documents within a folder so they appear at the top, as well as be able to sort them, similar to what you see on forums. This way for certain systems, there's a "Setup" or "READ THIS FIRST" sort of document that can sit at the top so that any important details are given first and foremost, rather than just having the documents sorted in alphabetical order. Additionally, the option to highlight them with a particular color, as you do with callouts within a document for example, would be cool too. This way a newbie can immediately go to the documentation, take note of the highlighted/stickied documents, and follow them accordingly. This would also be great for project teams who have upgraded systems so that the updated documentation gets more visibility. As it stands right now, best we can do is append document titles with a numerical value like "1 Read this first!" which leaves a lot to be desired. Thanks!

In large MSP environments, asset templates often contain a very high number of custom fields to cover all possible documentation needs. While this flexibility is essential, it also creates a usability problem in Hudu’s asset view: When a section heading (sub-header) contains only empty fields, the fields themselves are hidden as expected — but the section title still remains visible. This results in long pages filled with unused section headers, forcing technicians to scroll unnecessarily to locate the relevant information. Requested improvement We’d like to see Hudu automatically hide entire section headers (and their spacing) when all fields inside that section are empty or have no data to display. For example: • If the section “Network Interfaces” has no filled fields → the section title should be hidden entirely. • If at least one field under a section contains data → the section title and that field group should be shown normally. Optional enhancement • Admins could toggle this behavior globally or per template (e.g. “Hide empty sections by default”). • A small indicator could optionally be shown in edit mode to make it clear that hidden sections exist. Benefits • Cleaner, more focused asset views. • Faster access to relevant data without scrolling through empty sections. • Dramatically improved readability for templates with dozens or hundreds of potential fields. In short, we’re requesting that empty section headers in asset views be automatically hidden when no fields under them contain data — making complex asset layouts much more efficient and user-friendly.

Field type of IP address that requires either an IP address or an IP address with CIDR mask.

Could have an option inside the integration to map Expirations to a ticket type, and map the company so it generates a ticket under that company. E.g. Firewall Asset has a warranty expiry, that warranty expiry generates a sales ticket in the PSA so the team can quote for the re-warranty / replacement.

Many customers operate multiple interconnected locations — often linked through VPN or IPsec tunnels between firewalls or routers. It would be extremely valuable if Hudu could visualize and document these site-to-site connections, along with their associated network routes and subnets. The goal would be to create a complete logical network map inside Hudu, showing not only which devices exist in each location, but also how those locations communicate and which network segments are routed through which tunnels. For example: • Location A ↔ Location B (IPsec Tunnel 1 – 10.0.0.0/24 ↔ 10.10.0.0/24) • Location A ↔ Datacenter (VPN – 10.0.0.0/24 ↔ 172.16.0.0/24 via BGP) • Location B ↔ Cloud (SSL VPN – split routing enabled) Ideally, users could: • Define tunnel endpoints, type (VPN, IPsec, GRE, etc.), and status • Specify network segments/subnets that traverse each tunnel • Automatically visualize the connectivity map between sites and data centers • Optionally link each connection to the related firewall, router, or configuration documentation inside Hudu This feature would provide a clear, visual understanding of multi-site environments, making it much easier to design, document, and troubleshoot complex network topologies. It would also allow technicians and network planners to see how data flows between customer locations — directly from Hudu — and maintain accurate, centralized network documentation. In short, we’re requesting a VPN and routing topology view, enabling the definition and visualization of inter-site tunnels, routed subnets, and logical network paths within Hudu’s interface for a truly complete network overview.

Make it so that an KB article that is put in to a specific directory inherits the folder permissions. I have a HR Folder that I dont want normal staff to be able to edit but would like them to view.

We make extensive use of flags in Hudu to indicate the current state of documentation — for example: • 🟡 In Progress • 🔴 Outdated / Needs Review • 🟢 Reviewed / Up-to-Date • 💎 Verified / Production Ready However, documentation is never permanent. Even high-quality or recently verified entries eventually become outdated as systems, integrations, and processes evolve. Currently, flags in Hudu remain static unless changed manually, which often results in outdated material staying marked as “Up-to-Date” indefinitely. We propose adding flag expiration and automatic status transitions to help maintain documentation accuracy and freshness. Desired functionality • Each flag type can have an optional expiration period (e.g., 90 days, 6 months, 1 year). • When that period passes since the item was last updated or re-flagged, Hudu automatically downgrades the flag — for example: • Up-to-Date → Needs Review after 90 days of inactivity • Verified → Needs Re-Validation after 6 months • Admins can configure: • Default expiration values per flag type • Which flag should be applied when the current one expires • Whether notifications or reminders are sent to assigned users or groups Benefits • Keeps documentation automatically rotating through review cycles • Reduces manual maintenance overhead • Ensures content accuracy over time • Enables MSPs to easily identify stale or unverified materials In short, we’re requesting an enhancement where flags can expire and automatically revert to a review-needed state after a configurable period of time — enabling continuous, semi-automated documentation lifecycle management directly within Hudu.

For resellers and MSPs using Arrow (ArrowSphere) as their primary cloud distribution platform, it would be extremely valuable if Hudu could integrate directly with the ArrowSphere API to synchronize customer-specific subscription and billing data. The ArrowSphere API is fully documented here: 🔗 https://arrowsphere-api.readme.io/docs/welcome Desired functionality • Connect to the ArrowSphere API using secure credentials (API key / OAuth). • Automatically import and update customer subscriptions, including: • Product name (e.g., Microsoft 365 Business Premium, Defender for Business, etc.) • License quantity and status • Billing cycle (monthly / annual) and next renewal date • Subscription start date and provisioning ID • Associated customer / tenant name and domain • Display this information within the customer’s Hudu record — for example under a Licensing or Subscription section. • Optionally trigger flags or reminders when renewals are approaching or when a subscription status changes. • Allow linking between imported subscriptions and existing asset records (e.g., Intune tenant, Microsoft tenant documentation, or customer billing policies). Benefits • Provides a real-time view of all M365 and cloud subscriptions per customer directly in Hudu. • Eliminates manual data entry and reduces the risk of outdated license information. • Improves coordination between technical and billing teams by connecting operational data to contract and renewal dates. • Enables proactive renewal management and automated documentation updates through Hudu workflows. In short, we’re requesting a native ArrowSphere integration that uses the official API to synchronize Microsoft 365 product and billing information into Hudu, keeping subscription documentation accurate, automated, and directly tied to customer environments.