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

# Overview

> What the Liongard integration brings to your Neo Agent setup

Liongard inspects your clients' systems (Microsoft 365, Active Directory, firewalls, DNS, backups) on a schedule, records what changed, and raises Actionable Alerts when a rule finds a problem. Each client is an environment. Connect Liongard to Neo and your agents raise a ticket in your PSA for each new alert, with the finding and the fix, read the alert behind a ticket and the system it names, and list what changed on a client before a ticket came in.

> [!NOTE]
>
> Liongard uses one access key per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent.

## What Neo can do with Liongard

> **Alerts & Change Detections**
>
> Read each Actionable Alert's finding, priority, status and the action to take, per client, and every change Liongard detected on a client's systems.

> **Systems & Inspection Data**
>
> Read a system's latest inspection, its timeline, metric values and the client dashboard's numbers, such as users without MFA.

> **Launchpoints & Inspections**
>
> Run an inspection again after a fix to confirm the alert clears, and manage launchpoints and their schedules.

> **Agents & Asset Inventory**
>
> Find an agent that stopped checking in, empty its job queue, and read or update the client's devices and identities.

> **Environments & Metrics**
>
> Find or set up a client's environment, and read the values of the metrics you defined in Liongard.

> **Users & Webhooks**
>
> Give a technician access to Liongard or remove a leaver, and manage webhooks.

## Your clients are mapped automatically

Neo matches each Liongard environment to a company in your PSA and keeps the mapping on the Liongard card's **Organization Mapping** tab. It refreshes the mapping when you save the key, and again on each nightly PSA sync. A client with child environments (its sites) can have several environments mapped to one company.

Matching uses the environment's name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest.

**A name match, or one you confirm, is handed straight to your agents**, so they start from the client's environments without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent reaches only the environments mapped to the ticket's company.

## Next steps

> **[Connect Liongard](/integrations/liongard/connecting-to-neo)**
>
> Create an access key in Liongard, save it in Neo and choose what each agent can do.


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