> ## 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 SonicWall to Neo

> Generate a MySonicWall API key and save it in Neo

You connect SonicWall once at the MSP level, with a MySonicWall API key and the region of your NSM portal. Neo uses the key to sign in to NSM for each of your tenants.

## Before you start

* Your firewalls are managed in **Network Security Manager** in the cloud (`nsm-uswest.sonicwall.com` or `nsm-eucentral.sonicwall.com`), with at least an **NSM Essentials** licence, which SonicWall requires for API access.
* **API access** is enabled for your MySonicWall account. If MySonicWall does not offer **Generate My API Key**, ask SonicWall support to enable API access.

## 1. Generate the API key in MySonicWall

<Steps>
  <Step title="Sign in as the right user">
    Sign in to [MySonicWall](https://www.mysonicwall.com) as a user who can see every tenant you want Neo to reach. The key has that user's access in MySonicWall and NSM, so a read-only user's key cannot make changes.
  </Step>

  <Step title="Generate the key">
    Open **My Workspace** > **User Groups** > **User List** (on monthly billing accounts, **Access Management** > **Users**) and click **Generate My API Key**. Give it a description. Leave **Source IP Address** empty, or add Neo's IP addresses from [IP Whitelisting](/integrations/ip-whitelisting).
  </Step>

  <Step title="Copy the key">
    Copy the key before you close the window: MySonicWall does not show it again. A key lasts at most one year; generate a new one and save it in Neo before it expires.
  </Step>
</Steps>

## 2. Add the key in Neo

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

  <Step title="Save the key">
    Pick your NSM region, paste the API key, and click **Save settings**. Neo lists your tenants and signs in to NSM for one of them before saving, so a wrong key or region is rejected straight away.
  </Step>
</Steps>

## 3. Turn SonicWall 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 **SonicWall**, pick an access profile, or set each permission group by hand.

    | Profile | What it does |
    | - | - |
    | **Read Only** | Reports inventory, licences, firmware, VPN and link status, rules and security data; changes nothing |
    | **Helpdesk** | Also acts on alerts and reports on its own; every other change, devices and licences included, asks a technician |
    | **IT Admin** | Schedules firmware upgrades and restarts and changes VPN and network settings on its own; rules, security services, commits and administration ask a technician |
    | **Full Automation** | Every supported write without approval, except CLI commands, the administrator's password, removing a two-factor key, a bulk reset of firewall users' credentials, turning the management console off, access point factory resets and access-rule default restores, and removing a tenant or firewall |

    See [SonicWall API](/agents/tools/networking/sonicwall-api) for every permission group.
  </Step>

  <Step title="Tell the agent what to do">
    Add an instruction, for example: "Every Monday, list the SonicWall firewalls of every client whose licences expire in the next 30 days, with the service and the date, and post it as a report." Or: "When a VPN tunnel goes down, check the tunnel and the WAN link status in SonicWall and write what you find in an internal note."
  </Step>
</Steps>


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