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

# Connecting TP-Link Omada to Neo

> Create an Open API application on the Omada cloud controller and save it in Neo

You connect Omada once at the MSP level, with an Open API application on your Omada cloud controller: its Interface Access Address, Omada ID, Client ID and Client Secret.

## 1. Create the Open API application

<Steps>
  <Step title="Pick the view">
    Sign in to your Omada cloud controller as an administrator. To reach all your Omada customers, stay in the **MSP view**. To reach one organization's sites, open that organization's **Global view**.
  </Step>

  <Step title="Create the application">
    Open **Settings** > **Platform Integration** > **Open API** and add an application in **Client** mode. Give it a role that can manage the customers and sites Neo should reach.
  </Step>

  <Step title="Copy the values">
    Click **View** on the application and copy the **Interface Access Address**, the **Omada ID** (in the MSP view it is your MSP ID), the **Client ID** and the **Client Secret**.
  </Step>
</Steps>

<Warning>
  Changing the application's role, site or customer privileges, or copying or importing sites, makes Omada cancel the tokens it issued. Neo then gets a new token by itself. Deleting the application, or creating a new secret, stops Neo until you save the new values here.
</Warning>

## 2. Add the application in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open [**Integrations** → **TP-Link Omada**](https://dashboard.neoagent.io/integrations?open=omada), under Networking.
  </Step>

  <Step title="Save the application">
    Pick the account type (**MSP view** or **Single organization**), paste the Interface Access Address, Omada ID, Client ID and Client Secret, and click **Save settings**. Neo checks them against Omada before saving, so a wrong value is rejected straight away.
  </Step>
</Steps>

After you save, Neo maps your Omada customers (MSP view) or sites (single organization) to the companies in your PSA. Check and correct the matches on the **Organization Mapping** tab.

## 3. Turn Omada on per agent

<Steps>
  <Step title="Open the agent's integrations">
    Open the agent in the Neo Dashboard and go to its **Integrations** tab.
  </Step>

  <Step title="Pick an access profile">
    Under **TP-Link Omada**, pick an access profile, or set each permission group by hand.

    | Profile | What it does |
    | - | - |
    | **Read Only** | Reads Omada customers, sites, devices, clients, settings and logs; changes nothing |
    | **Helpdesk** | Reboots devices, reconnects or blocks clients, issues vouchers and resolves alerts on its own; other changes, and the changes Full Automation also asks about, ask a technician |
    | **IT Admin** | Makes every supported change on its own except the Firewall, VPN & Security and the Admins & Controller Settings groups, and the changes Full Automation also asks about, which ask a technician |
    | **Full Automation** | Makes every supported change without approval, except 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) |
  </Step>
</Steps>

The [TP-Link Omada API](/agents/tools/networking/omada-api) page lists every permission group and the changes that always ask a technician.

## Limits

* Neo connects to the Omada cloud controller only. A self-hosted Software Controller or an OC hardware controller cannot be connected.
* Neo cannot upload or download files (firmware images, backups, certificates, exports), run batch calls, transfer the controller's owner or change its cloud account binding.


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