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.

​
Overview

Hudu is an IT documentation platform that helps MSPs organize knowledge bases, asset information, passwords, and procedures. By integrating Hudu with MSPortal.ai, you can:
  • Access Hudu documentation, articles, and procedures directly from MSPortal
  • Browse and reveal passwords securely without leaving MSPortal
  • Map Hudu companies to your MSPortal companies for unified data access
  • Push compliance data from MSPortal to Hudu Magic Dash
  • Write MSPortal warranty dates back to Hudu assets
The Hudu connection page lists its tasks in the Setup guide: Connect, Choose data, Import or match companies, Configure warranty, Configure Magic Dash and Review. Choose data contains articles, procedures, password sharing and asset layouts. Configure warranty and Configure Magic Dash hold the outbound features that write to Hudu.
Hudu Choose data with Knowledge Base Articles, Procedures, Asset layouts and Enable Password Sharing switches side by side, each with an (i) beside its name, and the asset layout switches in a row below, with Configure warranty and Configure Magic Dash in the setup guide.

Branch preview: MSP staff in the Demo tenant.

​
Prerequisites

Before you begin, ensure you have:
  • Active Hudu account with administrative access
  • MSPortal.ai account with integration management permissions
  • Companies already set up in MSPortal (from your PSA integration or manually created)
Only one documentation integration can be active at a time. If you already have IT Glue connected, you must remove it before setting up Hudu. Go to Settings > Integrations, open the IT Glue connection, and choose More actions > Disconnect… first.
The Hudu integration maps companies to existing companies in MSPortal. Import your companies from your PSA integration first, or create them manually before setting up Hudu.

​
Part 1: Generate API Credentials in Hudu

Before connecting to MSPortal, you need to create an API key in your Hudu instance.
1

Log into Hudu

Access your Hudu instance at your organization’s URL (e.g., https://your-instance.huducloud.com).
2

Navigate to API Keys

Go to Admin > API Keys from the main navigation. Depending on your Hudu version, this may also be under Account Settings > API Keys.
3

Create a New API Key

Click New API Key and enter a descriptive name such as MSPortal Integration.
Use a descriptive name so you can easily identify this key’s purpose later. Avoid generic names like “API Key 1”.
4

Copy the API Key

After creating the key, copy it immediately and store it in a secure location.
Copy the API key now! It will not be displayed again after you leave this page. If you lose the key, you will need to generate a new one.
5

Note Your Instance URL

Make note of your full Hudu instance URL. This is the URL you use to access Hudu in your browser, for example:

​
Required Information

Before proceeding to MSPortal, ensure you have:

​
Part 2: Set up the connection in MSPortal

Open Settings > Integrations, choose the Directory tab and select Hudu. To maintain a saved connection, open it from your active integrations.

​
Connect

1

Enter Your Hudu Base URL

Enter the full URL of your Hudu instance in the Hudu Base URL field, such as https://your-instance.huducloud.com.
Include https:// at the beginning. Do not include a trailing slash or /api/v1. The instance must be reachable from the internet over HTTPS.
2

Enter Your API Key

Paste your Hudu API key into the API Key field.
3

Test the connection

Select Test connection to verify your credentials.If the connection fails:
  • Verify your Hudu Base URL is correct and includes https://
  • Check that your API key is copied exactly, with no extra spaces
  • Ensure your Hudu account has API access enabled
  • Confirm your Hudu instance is accessible from the internet (self-hosted instances behind a firewall may need configuration)
4

Save

Select Save and continue after a successful test. Testing alone does not create the connection. MSPortal starts fetching your Hudu companies in the background.
Your API key is stored securely using encrypted vault storage. It is never exposed in logs or API responses.

​
Choose data

In Choose data, choose what synchronizes from Hudu. The switches sit side by side; to read what one does, hover over or tap the (i) beside its name. Each switch saves as soon as you flip it. Turning a dataset off hides its dependent settings without clearing the saved choices. MSPortal fetches your asset layouts from Hudu in real time. Each layout represents a category of assets (e.g., “Network Devices”, “Software Licenses”, “Cloud Services”). Toggle individual layouts, use the search box to find one, or use Enable All / Disable All.
Enable All and Disable All change every layout in the connection, including layouts the search box is hiding.
Turning a type on starts a background sync, so content appears once that sync finishes. Use Run sync when fresh content is needed and check Sync activity. Check the synced content afterward rather than relying on the switch alone.

​
Password sharing

Before you turn on password sharing, be aware of how MSPortal handles Hudu passwords:
  • Password values are never stored in MSPortal. Only password names, usernames and URLs sync. Every time a user reveals a password, the value is fetched live from Hudu at that moment.
  • Every password reveal is audit-logged. MSPortal records which user viewed which password and when.
  • Access requires permissions. Users must have the read_documentation_passwords permission to reveal passwords.
When Enable Password Sharing is on, users with the read_documentation_passwords permission can browse and reveal passwords for mapped companies. It does not grant every Company user access to every password. Your Hudu API key must also allow password access, or reveals fail. Turning the switch off removes the synced Hudu password details from MSPortal. It does not delete anything in Hudu. Per-company password folder visibility and role-based access are set in Settings > Documentation > Passwords.
Use folder-level sharing to restrict access to sensitive credentials. For example, you might share a “General Access” folder while keeping “Domain Admin” passwords restricted.
Password sharing gives MSPortal users access to credentials stored in Hudu. Ensure only appropriate users have the read_documentation_passwords permission in MSPortal.

​
Import or match companies

Map your Hudu companies to MSPortal companies. This determines which documentation, assets, and passwords are accessible for each company.
  1. Wait for the initial company sync. After the connection is saved, MSPortal fetches your companies from Hudu. This may take a few moments depending on the number of companies in your account.
  2. Review the suggested matches. MSPortal suggests a company when a Hudu company’s id_number matches a PSA external company ID already imported into MSPortal, or when the names match ignoring case and whitespace.
  3. Accept a suggestion, choose another company in the row, or use Import company to create a portal company from it. Accept strong matches accepts every suggestion at 90% confidence or more after you review them.
  4. Choose Ignore for any Hudu company you never want to map. You can restore it later. Remove match unlinks a company.
Each accepted match, unlink and import saves immediately. Check for duplicates before you import a company.
You must map at least one company to finish setup. Only documentation, assets, and passwords from mapped companies will be accessible in MSPortal.

​
Configure warranty

The Warranty Writeback card writes MSPortal warranty dates to Hudu assets.
  1. Turn on Enable warranty writeback
  2. For each MSPortal device type, pick the Hudu asset layout, then its Serial number field, Warranty start field and Warranty expiration field
  3. Click Save warranty settings
Unlike the switches in Choose data, these settings do not save until you click Save warranty settings. Only assets with a unique serial number match inside the mapped company and layout are updated. See Warranty Writeback before you turn it on.

​
Configure Magic Dash

Hudu Magic Dash allows external tools to push summary data into company dashboards. When enabled, MSPortal pushes compliance status, security metrics, and device health data into Hudu for each mapped company, so your team can see this information without leaving Hudu. Turn on Enable Magic Dash in Configure Magic Dash. The switch saves immediately and starts the first push right away, before you select Finish setup. After that, data updates automatically on a regular schedule. This changes Hudu, so review the companies and expected compliance content before enabling it. Turning Magic Dash off stops future pushes. It does not remove items already written to Hudu.
Magic Dash and Warranty Writeback are the only parts of the Hudu integration where data flows from MSPortal to Hudu. All other data flows from Hudu into MSPortal.

​
Review and finish setup

Open Review and select Finish setup once the required tasks are complete. Skipping or leaving a task does not undo its saved settings.

​
What Gets Synced

Password values are unique in that they are never stored or cached in MSPortal. Each time a user reveals a password, it is fetched in real time from the Hudu API. This ensures passwords are always current and reduces the security risk of storing credentials in a second system.

​
Maintain the connection

Open the Hudu connection from Settings > Integrations and choose a task in the Setup guide to change its settings. Run sync in the connection header refreshes data from Hudu, and Sync activity shows each run’s result.
  • Rotate the API key: open Connect and enter the new key. The Hudu Base URL stays locked. Select Test connection, then Save changes. A test on its own does not store the replacement. Leave the mask unchanged to keep the stored key.
  • Map new companies: as you onboard new clients in Hudu, open Import or match companies. New Hudu companies appear in the list for you to match or import.
  • Disconnect: open More actions and choose Disconnect…. The confirmation lists the stored credentials, company matches and synced data that will be removed. It is not a way to revoke one client’s content access.

​
Troubleshooting

Causes:
  • Incorrect Hudu Base URL or API key
  • Hudu instance is not reachable from the internet
  • API key has been revoked or expired
  • Self-hosted Hudu behind a firewall
Solutions:
  1. Verify your Hudu Base URL includes https://, matches your browser URL exactly, and does not end in /api/v1
  2. Check that the API key is copied correctly with no extra spaces
  3. For self-hosted instances, ensure your Hudu server allows incoming API requests
  4. Generate a new API key in Hudu if the current one may be invalid
No. Test it, then select Save and continue and wait for success.
Causes:
  • Initial sync still in progress
  • API key lacks read permissions for companies
Solutions:
  1. Wait a few minutes for the initial company sync to complete, then check Sync activity
  2. Verify your API key has read access to companies in Hudu
  3. Check that your Hudu instance has at least one company configured
Causes:
  • Company names differ between Hudu and MSPortal
  • Hudu companies do not have id_number values set
Solutions:
  1. Choose the company in the row for companies with different names
  2. Add id_number values to Hudu companies if you want ID-based matching
  3. Ensure company names are consistent across both platforms where possible
Causes:
  • Password sharing not configured for the company
  • User lacks the read_documentation_passwords permission
  • Specific folders selected but the password is in a different folder
  • The Hudu API key does not allow password access
Solutions:
  1. Open Choose data and verify Enable Password Sharing is on
  2. Check that the user has the read_documentation_passwords permission under Settings > Users and Roles
  3. If using folder-level sharing, verify the correct folders are selected in Settings > Documentation > Passwords
  4. Confirm the Hudu API key allows password access
Causes:
  • Content type (articles, assets, procedures) is toggled off
  • Company is not mapped
  • The sync has not finished
Solutions:
  1. Open Choose data and enable the desired content types
  2. Verify the relevant asset layouts are toggled on
  3. Confirm the company is matched in Import or match companies
  4. Check Sync activity for the latest run
  5. If MSP staff see the content but company users do not, review sharing in Settings > Documentation
No. Sync selection and client visibility are separate. Configure the intended company and role access in Documentation settings.
Causes:
  • Magic Dash not enabled
  • Company mapping incomplete
Solutions:
  1. Open Configure Magic Dash and turn on Enable Magic Dash
  2. Verify the company is matched in Import or match companies
  3. Confirm MSPortal has compliance data for that company to push
No. Content, sharing and Magic Dash switches already saved remain saved. Warranty mappings have their own explicit save.

​
Best Practices

Map Companies First

Complete company mapping before configuring documentation, passwords, or Magic Dash. All other features depend on accurate company mappings.

Accept Strong Matches

Review the suggestions, use Accept strong matches for the confident ones, then match the rest by hand. It saves significant time for large environments.

Restrict Password Access

Use folder-level password sharing to limit which credentials are accessible. Only grant the read_documentation_passwords permission to users who need it.

Audit Password Access

Regularly review the audit log to monitor which users are accessing passwords. This helps maintain accountability and detect unusual access patterns.

Keep Names Consistent

Maintaining consistent company names between Hudu and your PSA makes suggested matches more accurate and reduces manual mapping effort.