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

# Level

> Let Neo agents find a ticket's device in Level, read its inventory, alerts and patches, tag and move devices, and run your Level automations as remediation scripts

Level is a cloud RMM: its agent on each Windows, macOS and Linux device reports hardware, operating system, security and patches, monitors raise alerts, and automations run scripts on devices. Connect it once with a Level API key, and Neo agents can read and act on your customers' devices.

## What Neo can do with Level

* Find the device a ticket is about, by hostname, serial number or the user who last signed in, and add its health to the ticket: online or last seen, disks and free space, memory, CPUs, operating system and end-of-life status, network addresses, security score
* Read a device's active alerts and its pending or failed operating system updates, and resolve an alert once its cause is fixed
* Run one of your Level automations on a device as a remediation script, through the automation's webhook trigger, and read each step's status and output
* Tag and untag devices, rename a device, change its notes, move it to another group, and set custom field values on a device or group
* Read your groups, tags, custom fields, automations and the Level activity log
* Answer questions in a chat with Neo about a customer's devices, alerts and patches

## Each ticket stays with its customer

One Level key reaches every device in your Level organization. Level has no customer record, so Neo treats each customer's own group as the customer. On a ticket that names a company, Neo sends a call only for the Level group the ticket's company is mapped to: every device, group, alert, update and automation run the call names must sit in that group or a group under it, and a device list must be narrowed to it. A customer's group that holds another customer's mapped group gets no Level calls on its tickets, because Level's group-wide reads and writes would reach the other customer: move the other customer's group out of it in Level, or map the customer to a group that holds only its own devices. Changes to what every customer shares (creating, renaming or deleting a tag or a custom field) run only outside a ticket run, such as from a scheduled agent or a chat with Neo.

## Automations run through webhook triggers

Level's API starts an automation through a **webhook trigger** on it. Neo runs only automations that have one, on the devices it names; it never runs an automation without naming its devices. Neo keeps each webhook's secret token to itself: agents refer to a trigger by its id, and the token never appears in a run, a ticket note or a script's output.

## Custom field values stay in Level

Custom fields often hold passwords, BitLocker recovery keys and other secrets, under any name. So Neo hides every custom field value from every agent and script, and the details of custom field changes in the activity log. Agents can still set a value; a technician reads values in Level.

## Some changes always ask first

Deleting a device or a group always waits for a technician's approval, whatever the agent's settings. Every other change, an automation run included, follows the preset you pick.

## Your groups are mapped to companies

Neo matches your Level groups to the companies in your PSA and keeps the mapping on the Level card's **Organization Mapping** tab, refreshed on each PSA metadata sync. Every group is listed by its path, such as `Customers / Contoso`.

Matching uses the group name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for top-level groups.

**A group whose name matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents.** Only the highest matching group in a branch is linked, so a site group under a customer's group is never linked on its own. A name two of your PSA companies share (`Acme` against `Acme Inc` and `Acme LLC` too), or two groups that match one company, is left to the AI match, and an AI match waits for you on the Organization Mapping tab. Confirm or correct each there.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right group by hand, a nested one included. A mapping you set by hand survives every later sync.

See [Level API](https://docs.neoagent.io/agents/tools/rmm/level-rmm-api.md) for the permission groups.

## Next steps

> [card] [Connect Level](https://docs.neoagent.io/integrations/level-rmm/connecting-to-neo.md)
>
> Create an API key and save it in Neo.


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