> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rallied.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Hudu

> Connect Hudu so the agent can read your IT documentation, asset records, knowledge base articles, processes, and passwords during ticket diagnosis.

Connect Hudu so every client agent can read your existing IT documentation — companies, assets, knowledge base articles, processes, and passwords — the same way a senior technician would when handling a ticket.

<Note>
  Hudu is configured in **MSP Settings → Integrations**.
</Note>

## How to connect

Hudu uses API key authentication. You'll need an API key from your Hudu instance before starting.

<Steps>
  <Step title="Generate a Hudu API key">
    Sign in to Hudu as an admin and go to **Admin → API Keys**. Click **+ Add new API Key**, give it a recognizable name (e.g. `Rallied Integration`), and copy the key — it's shown only once.
  </Step>

  <Step title="Open MSP Integrations">
    In the Rallied.ai dashboard, navigate to **MSP Settings → Integrations**.
  </Step>

  <Step title="Connect Hudu">
    Find the Hudu card and click **Connect**. A credentials form appears.
  </Step>

  <Step title="Enter your credentials">
    Fill in:

    * **API Key** — the key you generated above
    * **Hudu URL** — your Hudu hostname (e.g. `yourdomain.huducloud.com`). You can paste the full URL with `https://`; Rallied.ai normalizes it for you.
  </Step>

  <Step title="Save and confirm">
    Click **Save**. Rallied.ai validates the key against your Hudu instance, fetches your companies, and imports them as candidate client mappings. The card shows **Connected** when complete.
  </Step>
</Steps>

## Mapping companies to clients

Hudu stores documentation per **company**. To use Hudu with a specific Rallied client, map the client to its Hudu company on the client's detail page. Once mapped, every tool call the agent makes against Hudu is automatically scoped to that company — there is no risk of pulling another client's runbook into a response.

If a client is not mapped to a Hudu company, the agent will not consult Hudu when handling that client's requests.

<Note>
  The **Internal** company in Hudu — the one representing the MSP itself — is excluded from client mapping. Central KB articles and global processes are still indexed as MSP-wide documentation and available to every client agent.
</Note>

## What the agent reads

During diagnosis, the agent searches Hudu for content relevant to the request. The most useful surfaces are:

| Surface       | Typical content                                                        |
| ------------- | ---------------------------------------------------------------------- |
| **Companies** | Client records, contact info, top-level overview                       |
| **Assets**    | Servers, devices, software, custom asset layouts your team has defined |
| **Articles**  | Knowledge base articles, runbooks, "how we do X for client Y"          |
| **Processes** | Documented procedures and SOPs (called *Processes* in the Hudu UI)     |
| **Passwords** | Service accounts, admin credentials, shared logins                     |

The agent reasons about what's relevant from the request, fetches matching records, and either uses the information directly or includes it in its internal note for technician review.

## Passwords and approval

Passwords retrieved from Hudu are sensitive. The `hudu-get-password` tool returns the decrypted secret, so the agent is instructed to record in its notes why the credential was accessed. For especially sensitive operations, you can also require [identity verification](/agents/identity-verification) before the agent uses any retrieved credential, or change the policy from **Auto** to **Approval needed** in **MSP Settings → Integrations**.

## Tools

| Tool                  | Default policy  | Description                                                               |
| --------------------- | --------------- | ------------------------------------------------------------------------- |
| `hudu-search`         | Auto            | Full-text search across companies, assets, articles, and passwords        |
| `hudu-list-companies` | Auto            | List companies, optionally filtered by name                               |
| `hudu-get-company`    | Auto            | Get full details for a single company                                     |
| `hudu-list-assets`    | Auto            | List assets for the mapped company, optionally filtered by name or layout |
| `hudu-get-asset`      | Auto            | Fetch full details for an asset                                           |
| `hudu-list-articles`  | Auto            | List knowledge base articles, optionally filtered by name or company      |
| `hudu-get-article`    | Auto            | Fetch a knowledge base article by ID, including full content              |
| `hudu-list-passwords` | Auto            | List password records (names and metadata only — no secret values)        |
| `hudu-get-password`   | Auto            | Retrieve the decrypted password value for a record                        |
| `hudu-create-article` | Approval needed | Create a new knowledge base article                                       |

Read tools default to **Auto** so the agent can consult documentation freely during diagnosis. Write tools default to **Approval needed**.

## Policies

You can fine-tune Hudu tool policies from **MSP Settings → Integrations** (open the Hudu detail page). Policies can also be overridden per client from the client's detail page.