> ## 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 TP-Link Omada integration brings to your Neo Agent setup

TP-Link Omada is the network hardware many MSPs run at their clients' sites: gateways, switches and access points managed from the Omada cloud controller. When you connect Omada to Neo, your agents can see your Omada customers and sites, check which devices and clients are online, and make the changes you allow, without you opening the Omada console.

<Info>
  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](/integrations/omada/connecting-to-neo) has the steps.
</Info>

## What Neo can do with Omada

<CardGroup cols={2}>
  <Card title="Customers & Sites" icon="building">
    Find the Omada customer and site behind a ticket, and every device across them with its online state.
  </Card>

  <Card title="Devices" icon="wifi">
    Read access points, switches and gateways with their uplinks, ports and WAN health; reboot a device or power-cycle a PoE port.
  </Card>

  <Card title="Clients" icon="laptop">
    Find the user's device behind a complaint, with its access point, signal and connection history; reconnect or block it.
  </Card>

  <Card title="Networks, WiFi & Firewall" icon="shield-halved">
    Read and change SSIDs, VLANs, DHCP reservations, firewall rules, port forwarding and VPN.
  </Card>
</CardGroup>

Hotspot vouchers, alerts and events, site templates and controller admins are also available.

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

<Card title="Connecting TP-Link Omada to Neo" icon="plug" href="/integrations/omada/connecting-to-neo">
  Create the Open API application, save it in Neo, and pick access per agent.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.