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

> Create a Level API key, save it in Neo, and add webhook triggers to the automations Neo may run

You connect Level once at the MSP level. One API key covers every device in your Level organization.

## 1. Create the API key

**1. Open API keys**

Sign in to [app.level.io](https://app.level.io) as an administrator and go to **Settings**, **API keys**.

**2. Create the key**

Click **+ Create API key**, enter a description such as `Neo`, and pick the access level. **Read and write** lets agents tag and move devices, resolve alerts and run automations. **Read-only** lets them read only. Click **Create key** and copy it.

> [!WARNING]
>
> Deleting the key in Level cuts Neo off at once. Save the new key here when you replace it. A key you change to Read-only refuses Neo's writes from the next call.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Level card, under RMM (it also lists under Other).

**2. Save the key**

Paste the API key and click **Save settings**. Neo checks it against Level before saving, so a wrong key is rejected straight away.

**3. Check the mapping**

Open the card's **Organization Mapping** tab and confirm each customer's Level group is matched to the right PSA company. A ticket run acts only for a mapped group and what sits under it.

## 3. Let Neo run your automations

Neo runs a Level automation through its webhook trigger. For each automation you want agents to run as a remediation script (a disk cleanup, a service restart, a patch run):

**1. Add a webhook trigger**

In Level, open the automation's **Pipeline** and add a **Webhook** trigger. Turn on **Require an authorization header**, so only a write-enabled key from your organization can fire it.

**2. Set its condition**

Pick the devices it may run on, such as **All devices**. Neo always names the device; the condition still applies.

**3. Map its inputs**

If the automation needs an input (a user name, a path), add a parameter mapping for it. Neo sends each mapped parameter it has a value for.

Give each automation a clear name and description: the agent picks the automation by what they say it does.

## 4. Turn Level on per agent

Open the agent, go to its **Tools & Settings** tab, click **Other**, and expand the **Level** block. Pick one of its **Presets**, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Devices** | Disabled, Read Only, Read / Write | Devices with their hardware, operating system, disks, network and security detail; renaming, notes, moving and deleting a device. Turn on for every Level agent. |
| **Groups** | Disabled, Read Only, Read / Write | The group tree; creating, renaming, moving and deleting a group, and putting devices in a group or taking them out. |
| **Alerts** | Disabled, Read Only, Read / Write | Monitor alerts per device, and resolving one. |
| **Updates** | Disabled, Read Only | Pending, installed and failed operating system updates per device. |
| **Automations** | Disabled, Read Only, Read / Write | Your automations and their webhook triggers, running one on a device, and each run's step output. |
| **Tags** | Disabled, Read Only, Read / Write | Tagging and untagging devices, and creating, renaming and deleting a tag. |
| **Custom Fields** | Disabled, Read Only, Read / Write | Custom fields on the organization, a group or a device, and setting their values. Neo never shows an agent a value. |
| **Activity Log** | Disabled, Read Only | Who changed what, automation runs, sign-ins and settings changes. |

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read, and resolving an alert | Device changes, tags and automation runs; group and custom field changes are not allowed |
| **IT Admin** | Every read, device changes, tags, alerts and automation runs | Group and custom field changes, and deleting a device or a group |
| **Full Automation** | Every read and write | Deleting a device or a group |

See [Level API](https://docs.neoagent.io/agents/tools/rmm/level-rmm-api.md) for what the agent can read and change.


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