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

# Hudu API

> Read and write Hudu resources — articles, assets, asset layouts, companies, passwords, infrastructure, and more

The Hudu API tool gives Neo agents direct access to the Hudu REST API — read, create, update, and delete Hudu resources during ticket resolution.

<Info>
  Automatically enabled when you configure Hudu permissions in your agent workflow. No manual toggle needed. See the [Hudu integration page](/integrations/documentation/hudu) for the full permission model.
</Info>

## What It Does

* Look up companies, articles, assets, and procedures
* Create and update knowledge base articles based on ticket resolutions
* Manage asset records and their structured fields
* Browse asset layouts (schemas) and documentation folders
* Read and manage network infrastructure documentation — networks, VLANs, IPAM, racks
* Retrieve passwords (with technician approval)
* Access any Hudu API endpoint with permission-group-based access control

## Permission Groups

| Permission Group   | What It Covers                                                     |
| ------------------ | ------------------------------------------------------------------ |
| **Companies**      | Companies, relations, activity logs, matchers, integration cards   |
| **Articles**       | Knowledge base articles, procedures, uploads, public photos        |
| **Assets**         | Asset records — structured data entries created from asset layouts |
| **Asset Layouts**  | Asset layout definitions — the schemas that define asset structure |
| **Passwords**      | Asset passwords and password folders                               |
| **Folders**        | Documentation folders for organizing articles                      |
| **Infrastructure** | Networks, VLANs, VLAN zones, IP addresses (IPAM), rack storages    |
| **Websites**       | Monitored website entries — uptime and SSL tracking                |

Each group has an access level: **Disabled**, **Read Only**, or **Read/Write**.

## Access Profiles

<AccordionGroup>
  <Accordion title="Read Only">
    All groups Read Only. Agent can look up any resource but cannot modify.
  </Accordion>

  <Accordion title="Documentation Manager">
    Articles, Assets, Folders, and Websites at Read/Write. Everything else Read Only.
  </Accordion>

  <Accordion title="Full Access">
    All groups Read/Write with delete enabled. Password writes still require technician approval; company deletion is always blocked.
  </Accordion>
</AccordionGroup>

## Safety Controls

| Control                    | Behavior                                                                |
| -------------------------- | ----------------------------------------------------------------------- |
| **Technician-in-the-Loop** | Require human approval for writes — configurable per group              |
| **Password protection**    | All password writes always require approval, regardless of settings     |
| **Company safety**         | Agents can never delete companies                                       |
| **Delete control**         | Delete permissions off by default, must be explicitly enabled per group |

## How to Configure

<Steps>
  <Step title="Connect Hudu">
    [Connect your Hudu instance](/integrations/documentation/hudu) with an API key in the Neo Dashboard.
  </Step>

  <Step title="Configure permissions">
    In your agent workflow's **Integrations** tab, choose an access profile or customize each permission group.
  </Step>

  <Step title="Set approval requirements">
    Decide which permission groups require technician approval for writes.
  </Step>
</Steps>

<Tip>
  Start with **Read Only** and gradually expand. Enable Technician-in-the-Loop for writes until you're confident in the agent's behavior.
</Tip>