Skip to main content
Connect Hudu to synchronize company documentation, assets and procedures. Password sharing, Magic Dash and warranty writeback are separate choices. This setup is for MSP staff with integration management permission; publishing content to Company users also requires the appropriate Documentation settings access.

​
Before you start

MSPortal permits one active documentation platform: Hudu or IT Glue. Review an existing connection before replacing it; deleting a working connection removes its synchronized data and credentials. Have a publicly reachable HTTPS Hudu instance URL and an API key scoped to the companies and resources you need. In Hudu, an admin can create a key under Admin > API Keys. Password access and company scope are key-level choices. See Hudu REST API setup. A Magic Dash-only key is not sufficient for the full documentation integration.

​
Connect and map

1

Open Hudu setup

Open Settings > Integrations and connect Hudu. Use Configure on a saved Hudu connection when maintaining it.
2

Test the new connection

On Connect, enter Hudu Base URL, such as https://company.hudu.com, without /api/v1. Enter API Key and select Test Connection. Review the result before continuing.
3

Create the connection

Select Create Integration, wait for success, then Next. Testing alone does not create it. Company discovery runs in the background.
4

Map companies

On Map Companies, review Quick Match proposals or select the intended MSPortal company manually. Save pending links with Import Selected or Next. Creating a missing MSPortal company saves it immediately, then stages its link. Removing an existing link saves immediately.
Blank Hudu base URL and API key form before testing or creating a connection.

​
Choose Documentation

Use Knowledge Base Articles, Procedures and the Asset Layouts switches to choose what synchronizes. Each change saves immediately. Enable All and Disable All affect all layouts for this connection, including layouts hidden by the search. Search narrows the list you see, not the scope of those bulk controls. Next from the mapping and configuration steps can request background content synchronization. A successful toggle or wizard completion does not prove that articles have arrived. Inspect the synchronized content and its freshness afterward. The Warranty Writeback card has a separate draft and Save warranty mappings button. Its switch does not follow the immediate-save behavior of the content switches. See warranty writeback before enabling it.

​
Configure Passwords

On Passwords, Enable Password Sharing saves immediately. It enables the integration’s sharing feature and password-metadata synchronization. It does not grant every Company user access to every password. Review Settings > Documentation > Passwords for folder and role visibility, and check that the Hudu key permits password access. Password values are requested from the provider when an authorized reveal is used; a synchronized password entry does not prove that reveal will succeed. Use the password reader for the user workflow.

​
Decide whether to enable Magic Dash

Enable Magic Dash saves immediately and requests a background push of available company compliance information to Hudu. It can start before Complete Setup. This changes Hudu; it is an optional outbound feature, separate from importing documentation. Review the mapped companies and inspect the actual Hudu result before relying on it. Do not assume every security, patching or training metric is included simply because the setup card lists examples. Turning the feature off stops future enabled pushes; it does not serve as an undo for content already written to Hudu.

​
Share content and maintain credentials

After synchronization, use Settings > Documentation to set the intended content and Company-role visibility. Connecting Hudu and enabling a layout do not by themselves complete client sharing. Some Hudu article-sharing actions also enable public sharing in Hudu; read the confirmation before proceeding. For key rotation, reopen Connect, enter the replacement and use Update API Key. The existing Base URL is locked. An update-success message confirms storage; run Retest Connection afterward to verify the saved key against Hudu. A retest on its own does not store a replacement. Skip, Back and Complete Setup are navigation controls, not an undo for settings already saved. The footer Delete confirmation disconnects the integration; it is not a way to revoke one client’s content access.

​
Troubleshooting

​
Frequently asked questions

MSPortal supports one active documentation platform. Review the existing connection before replacing it; deleting it removes synchronized data and credentials.
No. Test it, then select Create Integration and wait for success.
Yes. Each change saves immediately. Enable All and Disable All apply to all layouts for the connection, including search-hidden layouts.
No. Check provider key password access, portal permissions, company mapping and folder/role visibility in Documentation settings.
No. The switch saves immediately and requests the background push. Review the companies and expected compliance content before enabling it.
It confirms the credential update. Use Retest Connection afterward to verify the saved key against Hudu.
No. Content, sharing and Magic Dash switches already saved remain saved. Warranty mappings have their own explicit save.
Sync selection and client visibility are separate. Configure the intended company and role access in Documentation settings.

Read documentation

Find synchronized and native content.

Company mapping

Review linking and persistence.

Warranty writeback

Configure deliberate provider updates.

IT Glue setup

Review the alternative documentation provider.