> ## 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.

# Overview

> What the Ubiquiti UniFi integration brings to your Neo Agent setup

UniFi is the network hardware most MSPs run at their customers' sites — gateways, switches and access points, managed through UniFi Site Manager at unifi.ui.com. When you connect UniFi to Neo, your agents can see every console and site your account manages, check which devices and clients are online, and — with a technician's sign-off — restart a device or change a network without you opening the UniFi console.

<Info>
  UniFi uses a single Site Manager API key per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent.
</Info>

## What Neo can do with UniFi

<CardGroup cols={2}>
  <Card title="Consoles & Sites" icon="server">
    List the consoles and sites your account manages, every device across the fleet with its online state, and ISP latency, packet-loss and uptime metrics.
  </Card>

  <Card title="Devices" icon="wifi">
    Read a site's access points, switches and gateways with live statistics; restart a device, power-cycle a PoE port or adopt hardware — always with technician approval.
  </Card>

  <Card title="Clients" icon="laptop">
    Find the client behind a connectivity complaint — IP, MAC, uplink device, signal, uptime — and, with technician approval, authorize or revoke guest access.
  </Card>

  <Card title="Networks, WiFi & Firewall" icon="shield-halved">
    Read and, with technician approval, change networks and VLANs, SSIDs, WANs, VPNs, DNS policies, firewall policies and ACL rules.
  </Card>
</CardGroup>

Hotspot Vouchers is also available — generating a guest WiFi voucher is the routine helpdesk write.

## Why connect UniFi

* **Check the network before touching the ticket.** A "WiFi is slow" or "internet is down" ticket gets answered from the gateway's WAN status, the AP's client count and the client's signal — not from a round trip to the console.
* **The whole fleet in one place.** The Site Manager cloud view spans every customer console your account can see, so an agent can tell which site a device belongs to without knowing the console's address.
* **Device restarts, any network or firewall change, and guest authorization always require a technician's sign-off**, no matter how automated the rest of the agent is — this is by design. The [UniFi API tool](/agents/tools/networking/unifi-api#safety-controls) reference lists every action that always needs approval.

## How agents reach UniFi

When you enable any UniFi permission group on an agent, Neo automatically adds the UniFi tool to that agent's toolbox. Per-console detail (clients, SSIDs, firewall) is reached through Ubiquiti's cloud Connector, so there is no VPN, port forward or per-site address to configure — UniFi OS consoles on firmware 5.0.3 or newer that are adopted into Site Manager just work. A self-hosted UniFi Network Server shows up in the fleet view (consoles, sites, devices) but Ubiquiti's Connector cannot reach into it for per-site detail.

## Where to go next

<Card title="Connecting UniFi to Neo" icon="plug" href="/integrations/unifi/connecting-to-neo">
  Setup steps for the API key, per-agent access levels, and the safety controls that stay in place.
</Card>