If you want to give clients better access to their own documentation, 2.47 brings a major overhaul to how client portals work.

What's happening: Client portals are being replaced by a portal user role built directly into core Hudu — not a separate interface anymore. Existing portal members auto-convert to portal users. No manual re-invite needed.

What portal users keep/gain:

• Still read-only — no creating or editing records

• Multi-company access via groups, instead of being locked to one assigned company

• Access to Central KB, My Vault, and Hudini AI, if you choose to enable them

Worth doing now, while you're on 2.46:

1. Grab the Portal Member Export (Admin > Export Data) — only available in 2.46, so we recommend not skipping it

2. Grab the Portal Record Export to see what's currently shared per client

3. Start planning your groups — company access becomes group-based, and converted members land in a temporary, heavily restricted, "Previously ungrouped portal users" bucket at 2.47 until you sort them

We wrote up the full why behind this change here: Portal users are moving to core

And the full what-to-expect / prep guide (includes a sample client email template you can send your end-users) here: Upcoming portal changes: what to expect and how to prepare

We don't have an exact release date for 2.47 yet, but we'll share it as soon as it's confirmed — we want to give you as much time as possible to prep and inform your clients.

We'll also be covering these changes and how to prepare in our Q3 webinar. Register here.

Happy to answer questions in the comments!

we're an MSP in Germany using Hudu self-hosted. Our technicians are happy with the English interface, but everything our clients see is English too: password and information requests, portal invitations, the login page and notification emails. Our clients communicate with us in German, and many of them aren't very technical, so English emails and pages confuse them and look out of place.

Two things would help us a lot:

• Customizable email templates: being able to edit subject and body of all client-facing emails (password and information requests, invitations, notifications), ideally with placeholders and per company.

• Customizable sign-in pages: adjusting the login and portal pages with our own wording, branding and language.

A language setting for client-facing texts would be the next step, but custom templates alone would already solve most of it.

I'm curious whether other Hudu users, especially from Germany, Austria and Switzerland or other non-English countries, run into the same issue. If enough of us need this, it might be a good candidate for Hudu to pick up, especially with the portal overhaul coming up. We'd be happy to help with translations, testing or reviewing German wording.

A question for Hudu and the self-hosters: is there any supported way to customize these texts today, for example templates or settings we might have missed? Modifying files inside the container isn't an option for us, since changes would be lost or break with every update.

Thanks!

Lars, LNIT

we run Hudu self-hosted and have been testing Hudini v2 and the new Semantic Search. Most of our KB is client documentation, so keeping AI processing on our own infrastructure matters to us for data protection reasons.

Semantic Search already runs entirely through our internal LLM gateway. All articles are indexed, and the results are very good, including for German content.

Where we're stuck: Hudini chat and Semantic Search share one provider connection, so once it serves embeddings, the chat can't use a separate local model. A self-hosted or OpenAI-compatible option isn't offered in the provider list either.

We've upvoted the existing requests for local LLM support and custom endpoints, and submitted a new request to separate the Semantic Search provider from Hudini chat: [Feedback - Hudu]. If this matters to you too, an upvote would help.

Has anyone solved this differently, or found another way to run Hudini chat on a local model? We'd love to hear how others are approaching it.

Thanks!
Lars, LNIT

This patch includes a few bug fixes. Self-hosted environments may update at any time; updates to cloud hosted environments will begin today.

Fixes

• Fixed a bug causing user specific 500 errors when a password folder was present in a company's 'Most Visited'

• Fixed a bug causing an infrequent 500 error on the Admin→Activity Logs page.

• Fixed a bug causing sync failures for the ConnectWise Integration by skipping company name conflicts.

• Fixed a bug preventing asset password/confidential text fields from loading on mobile.

Minimum suggested versioning for self-hosted

postgres: 18.6 w/ pgvector .8+

• Self hosted instances must have postgres 18+ and pgvector .8+ installed for this version. Follow our support guide here.

redis: 7.2.4-alpine

nginx: 1.31.2

Also in Community Scripts on GitHub

Folder structure, article edit history, and any related/attached items will shoot right over without a fuss.

To give it a try

you can open a new powershell 7 session and execute any of the following oneliners. Not to worry- you'll be asked at the end if you really want to move anything.

Ninja-Oneliner [Ninja-Style]

$script = [scriptblock]::Create((irm 'https://raw.githubusercontent.com/Hudu-Technologies-Inc/Community-Scripts/refs/heads/main/Administration/Moving-Bulk-Articles/Article-Wizard.ps1')); & $script -Wizard

Clone+Start [Samurai-Style] (requires git)

git clone https://github.com/Hudu-Technologies-Inc/Community-Scripts.git;  cd .\Community-Scripts\Administration\Moving-Bulk-Articles;  . .\Article-Wizard.ps1 -Wizard;

Download-Extract-Run [Ashigaru-Warrior-Style]

Invoke-WebRequest 'https://codeload.github.com/Hudu-Technologies-Inc/Community-Scripts/zip/refs/heads/main' -OutFile .\Community-Scripts.zip; Expand-Archive -Path .\Community-Scripts.zip -DestinationPath .\Community-Scripts -Force; cd .\Community-Scripts\Community-Scripts-main\Administration\Moving-Bulk-Articles; . .\Article-Wizard.ps1 -Wizard;

Starting Out

These examples and the oneliners above use the -wizard switch, which guides you through the process step-by-step. This script can also run noninteractively. For more information and technical details, see Community Scripts Repo on Github

Select Your Strategy-

Most people will have three strategy options, depending on whether or not you actually have company or central kb articles.

Select your source-

You can select a group of articles by folder, individually, or by company, when applicable.

Selecting Specific Articles-

If you select by individual folders or articles, you can just keep selecting until finished, then enter 0, when complete.

Select your target

(when moving articles to a company)

Preview and Finalize-

Whether you want to move anything or not, I'm not here to judge, but you'll be able to make an informed decision.

You'll get a nice preview and you can even move one at a time if you aren't completely sure.

If you want to move them one-by-one, you can use Y to confirm each article being moved.

• Multiple Radar Service installations supported per Company

• Uses local adapter GUIDS to match existing collectors, otherwise creates a new one under the company

• Scopes Networks, Adapters, Device data properly under each collector, rather than the company.

• Generates separate network maps for each collector

• Uninstalling the app properly marks its collector inactive

• Agent requires explicit collector name during installation

Fixes

• Radar adapter status recovers to online after an adapter is seen again during a successful scan.

• Various other minor bug fixes & improvements.

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

• Implementation Services

• Consulting & Advisory

• Team Training

• IT Glue to Hudu Migrations

• Self-Hosted Hudu Support