Core Web App

Add a markdown editor option so users can write and edit content in markdown instead of pasting/importing/export with the current text editor.

With the new KB article editor, it would be nice to have some way to revert to having the toolbar at the top, similar to the old editor.

The new KB article editor adds too much space between lines in bulleted and numbered lists. This makes it hard for readers to tell which lines belong together as one list versus separate items. Request: Tighten line spacing within lists so grouped items read as a cohesive list, similar to the old editor's behavior.

Prior to 2.45.0, IP allow list controls didn't apply to the API. As of 2.45.0, they do, requiring customers to whitelist every IP their API integrations (CIPP, Halo, ScalePad, etc.) call from. Request: add a setting to exclude the API from IP allow list enforcement, so customers can opt back into the pre-2.45.0 behavior if they don't want IP restrictions applied to API traffic.

Currently, pasting from Excel either pastes an image (ctrl+v), or unformatted text (ctrl+shift+v). It would be great if pasting in the cells copied from Excel would automatically create a table in the new editor.

API keys currently support only two scopes: global (all companies) or a single company. There's no middle ground for a customer who wants a key limited to a subset of companies. Request Add a third scope option for API keys: company group. This would let an admin select a defined group of companies (rather than one company or all companies) that the key has access to. Use case An MSP with multiple internal teams or business units wants to issue API keys scoped to a specific set of clients, without granting access to their entire company list or having to manage a separate key per company.

API keys currently only offer a single "view passwords" permission, which also grants access to OTPs. There's no way to grant access to one without the other. Request Split this into two separate permissions on API keys: View passwords – grants access to stored passwords only View OTPs – grants access to OTP codes only This lets admins scope API keys more tightly, for example, issuing a key that can pull passwords for an integration without also exposing OTPS.

MSPs are usually invited as admins on their clients' UniFi consoles rather than owning them outright. Today the UniFi OS integration needs a key from the console owner, so those client consoles sync sites but never pull in devices. The ask is for a way to document device inventory using an admin-level key, even if that means bringing over less data than a full sync does. Getting the devices in is the main thing. Requiring the client's owner account isn't practical for most MSP relationships, and asking clients to hand over owner credentials is a non-starter.

Please add option to pin KB articles to the top of the KB list for a company.

Problem: MSPs manage projects in ConnectWise but Hudu has no way to pull that data in, so projects get manually duplicated or skipped in documentation. Request: Sync ConnectWise project records (name, status, company, dates) into Hudu, mapped to the right company.