You connect Omada once per MSP and every agent you enable can use it, with permissions you control per agent. Neo connects with an Open API application on your Omada cloud controller, created in the MSP view to reach all your Omada customers, or in one organization to reach its sites. Connecting TP-Link Omada to Neo has the steps.
What Neo can do with Omada
Customers & Sites
Find the Omada customer and site behind a ticket, and every device across them with its online state.
Devices
Read access points, switches and gateways with their uplinks, ports and WAN health; reboot a device or power-cycle a PoE port.
Clients
Find the user’s device behind a complaint, with its access point, signal and connection history; reconnect or block it.
Networks, WiFi & Firewall
Read and change SSIDs, VLANs, DHCP reservations, firewall rules, port forwarding and VPN.
Why connect Omada
- Check the network before touching the ticket. A “WiFi is slow” or “internet is down” ticket gets answered from the gateway’s WAN state, the access point’s load and the client’s signal.
- Every client in one place. With an application in the MSP view, an agent reaches every Omada customer you manage, and Neo maps each one to the matching company in your PSA.
- Changes follow your rules. Each permission group is off, read-only or read and write per agent, with technician approval where you want it. Deleting an Omada customer or site, restoring a backup, forgetting a device, changing admins, roles, SSO or two-factor authentication, and setting a secret (a password, key, PIN, token or SNMP community) always ask a technician.
Where to go next
Connecting TP-Link Omada to Neo
Create the Open API application, save it in Neo, and pick access per agent.