Skip to main content
UniFi is the network hardware most MSPs run at their customers’ sites — gateways, switches and access points. When you connect UniFi to Neo, your agents can see your sites, 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. How much they see depends on how you connect. Through UniFi Site Manager at unifi.ui.com, agents reach every console and site your account manages. Through a controller’s own URL, they reach that one controller.
You connect UniFi once per MSP and every agent you enable can use it, with permissions you control per agent. Pick one of three connection types: a Site Manager API key, a UniFi OS console’s own API key with its URL, or a self-hosted Network Server’s URL with a local admin’s username and password. Connecting UniFi to Neo says which one your controller needs.

​
What Neo can do with UniFi

Consoles & Sites

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. The fleet view and the ISP metrics come from the Site Manager cloud; a controller connection lists that controller’s own sites.

Devices

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.

Clients

Find the client behind a connectivity complaint — IP, MAC, uplink device, signal, uptime — and, with technician approval, authorize or revoke guest access.

Networks, WiFi & Firewall

Read and, with technician approval, change networks and VLANs, SSIDs, WANs, VPNs, DNS policies, firewall policies and ACL rules.
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. With Site Manager, the 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. A controller connection trades that cross-console view for direct access to one controller.
  • 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 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 console hardware (Cloud Gateways, Dream Machines, Cloud Keys) on firmware 5.0.3 or newer that is adopted into Site Manager just works. A UniFi Network Application that you or a provider such as HostiFi runs is different. Adopted into Site Manager it appears in the fleet view, but the Connector cannot reach it, so per-site detail (clients, SSIDs, firewall) needs a direct connection. A UniFi OS Server can also be refused by the Connector on the firmware version it reports to Site Manager, and then needs the same direct connection. Connect such a deployment by its own URL: a UniFi OS Server or console takes an API key created in that console, and a classic Network Server takes a local admin’s username and password. Choosing a direct connection trades the cross-console fleet view for that per-site detail. See Connecting UniFi to Neo.

​
Where to go next

Connecting UniFi to Neo

Setup steps for the API key, per-agent access levels, and the safety controls that stay in place.