Hudu v2.46 is live!
This release hands admins more control over their instance, what's visible, who can access it, while Hudini becomes a real assistant instead of a bolted-on chatbot. It's also a heads-up release: some prep now will make the upcoming portal overhaul painless.
Before you update: self-hosted instances need postgres 18+ and pgvector .8+ installed first. Follow the upgrade guide here
Get ready for the portal overhaul
Our next release, v2.47, replaces client portals with a free portal user role built into the main Hudu app, a major shift that expands what portal users can actually do. Existing portal members convert automatically, but there's real value in reviewing your setup first.
To help, 2.46 adds two temporary exports: Portal Member Export and Portal Records Export (Admin, under Exports). Pull these now so you have a clean record of your current portal structure before the migration.
Read the full portal changes breakdown here: Upcoming portal changes, what to expect and how to prepare
Hudini v2: your documentation, on demand
Hudini has been rebuilt from the ground up. Chat with it in a docked panel that stays out of your way, or fire a question straight from search using AI Search. Turn on semantic search and Hudini finds the right article or process by meaning, not just keyword match, so “how do we onboard a new client” surfaces the real SOP even if it's not titled that way.
Tag records directly in chat to give Hudini context, and run skills (formerly Prompt Rules) with / mid-conversation. Minimize it to a draggable shortcut anywhere on the browser edge, or close it entirely and reopen from “AI” in the top nav when you need it. Access is controlled per group, so you decide who gets it.
Requires OpenAI or Azure OpenAI for semantic search.
Client password requests, get credentials without the back-and-forth
Chasing down a client's Wi-Fi password or admin login usually means an email thread, a text, or a call. Now you can generate a secure request link tied to a password field, send it to a client (or anyone with the link) and they submit the value directly into Hudu without ever logging in.
Submissions land in a review queue, so nothing goes live until you accept it. Admins can restrict this feature to specific groups if you want tighter control over who can send requests.
Decide exactly which tools each group can see
Not every group needs access to every tool. Admins can now toggle Central KB, Passwords, Processes, IPAM, Racks, Assets, and more on or off, either for the entire instance or per individual group. Turning a tool off doesn't delete its records; it just hides them until switched back on.
This is especially useful for larger teams where junior techs shouldn't see Racks or IPAM yet, or where a group simply doesn't need certain modules cluttering their view.
Lock down Knowledge Base folders by group
Central KB and Company KB folders can now be restricted to specific groups, or marked admin-only, with subfolders automatically inheriting the parent folder's permissions. If you've been keeping sensitive SOPs in a separate tool because “everyone with KB access could see everything,” that reason is gone.
Important: KB folder deletion is now destructive. Prior to 2.46, deleting a folder moved its articles to “No folder.” Starting now, deleting a folder permanently deletes it, its subfolders, and every article inside them, no recovery. A confirmation dialog requires typing DELETE to confirm, and this action is now limited to admins and above. Worth a reminder to your team before anyone reaches for that trash icon.
Radar now supports multiple collectors per company
For clients with multiple locations or non-routable networks, Radar can now run a separate service install at each site, while keeping all networks, devices, scans, and network maps organized under one company in Hudu. No more juggling separate companies just to work around network segmentation.
Also in this release:
- Author and editor roles have been merged: the only real difference (record flagging) is now available to editors and spectators
- Pin important Central KB or Company KB articles so they stay at the top regardless of sort order
- Bulk archiving added to Admin, under Users
- Groups, under Access page now uses a multi-select picker for asset layout permissions, and groups no longer get all-layout access by default
- API keys now require unique names
- Hudu feature requests are now powered by Featurebase, with improved formatting
- Records created via MCP or Hudini now show clearly in activity logs
Fixes
- Search result counts now match filtered article counts
- Legacy dropdown asset fields with newline-separated options are editable again
- Tighter spacing on bullet/numbered lists; nested lists and code blocks no longer break list formatting
- Radar company links fixed on the License Keys page
- Draft/publish conflicts resolved: “Revert to Published Version” only appears when a published version exists
- Non-unique group name submissions now show proper error feedback
- Halo integration company sync now correctly pulls inactive clients
- Liongard integration uses user-facing device type aliases
- Admin, under Alerts table page size now applies correctly
- Editors no longer see “Make Global Template” on process runs
- Auvik sync optimized for lower resource use
- UniFi OS integration now matches on (hostId, siteId) instead of siteId alone
- Various other minor fixes
Minimum suggested versions for self-hosted: postgres 18.6 w/ pgvector .8+, redis 7.2.4-alpine, nginx 1.31.2
