> ## 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 Cloud Secure Edge to Neo

> Create an API key in a client's CSE Command Center and save it in Neo

You connect Cloud Secure Edge once for each client that uses it, with two values from that client's org: its Command Center address and an API key.

## 1. Create the API key in the Command Center

**1. Sign in to the client's Command Center**

Sign in to the client's CSE Command Center as an admin. As a SonicWall partner, you reach a client's org through your MySonicWall affiliation.

**2. Create the key**

Go to **Settings** → **Identity and Access** → **API Keys** and select **Add API Key**. Name it "Neo" and choose its **Scope**:

| Scope | What Neo can do |
| - | - |
| **ReadOnly** | Read users, devices, roles, policies, services and events. Enough to check users and device ownership |
| **PolicyAuthor**, **ServiceAuthor** | Also change roles and policies, or services |
| **Admin** | Also remove users and devices, ban devices and cap their trust |

Copy the key's secret. Store it until you save it in Neo.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open [**Integrations** → **SonicWall Cloud Secure Edge**](https://dashboard.neoagent.io/integrations?open=sonicwall_cse), under Access Management.

**2. Pick the client**

In **Customer**, choose the client this CSE org belongs to. The client must be on your **Companies** tab. For a second client, click **Add customer**.

**3. Save the address and key**

Enter the address you sign in to the Command Center at, usually `https://net.banyanops.com` (an org on another Command Center, such as `https://eucc.console.banyanops.com`, uses that address), paste the key's secret, and click **Save settings**. Neo reads one user with the key before saving: a wrong address, or a key that is mistyped or deleted, is rejected straight away. Neo cannot tell which client's org a key belongs to, so check that the key comes from this client's org.

> [!WARNING]
>
> When someone deletes the API key in the Command Center, Neo loses access to that client's CSE org at once. Create a new key and save it here.

## 3. Turn Cloud Secure Edge on per agent

**1. Open the agent's tools**

Open the agent in the Neo Dashboard, go to its **Tools & Settings** tab and click **Access Management**, or ask your Neo Support Agent to add SonicWall Cloud Secure Edge to it.

**2. Pick a preset**

Expand the **SonicWall Cloud Secure Edge** block and pick one of its **Presets**, or set each permission group by hand.

| Preset | What it does |
| - | - |
| **Read Only** | Reads users, devices and their ownership, trust, roles, policies, services and events; changes nothing |
| **Helpdesk** | Removes leavers' users and devices, bans a lost device or caps its trust, asking a technician before each change; everything else stays read only |
| **IT Admin** | Every change on its own, except roles, policies and threat profiles and the [writes that always ask](https://docs.neoagent.io/agents/tools/security/sonicwall-cse-api.md#writes-that-always-ask-a-technician), which ask a technician |
| **Full Automation** | Every supported call without approval, apart from the [writes that always ask](https://docs.neoagent.io/agents/tools/security/sonicwall-cse-api.md#writes-that-always-ask-a-technician) |

To check whether a user exists and whether their device is personal or company-owned, **Read Only** is enough: the agent needs **Users & Groups** and **Devices & Trust** at Read Only.


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