Skip to main content
You connect Liongard once at the MSP level. The key reaches every environment its user can reach in Liongard.

​
1. Create the access key

A key acts with the role of the Liongard user who creates it. Create it as a user whose role reaches every environment you want Neo to work with, such as a dedicated integration user.
1

Open Account Settings

Sign in to Liongard as that user, open the profile menu at the top right, and click Account Settings.
2

Generate a token

Open the Access Tokens tab and click Generate New Token.
3

Copy the key and the secret

Copy the Access Key ID and the Access Key Secret. The secret shows only once.

​
2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Liongard card, under Documentation.
2

Save the instance and the key

Enter your instance, the address you sign in to Liongard at (for example us1.app.liongard.com or aus1.app.liongard.com), paste the Access Key ID and the Access Key Secret, and click Save settings. Neo checks them against Liongard before saving, so a wrong key or instance is rejected straight away.

​
3. Turn Liongard on per agent

Open the agent, go to its Tools & Settings tab, click Security, and expand the Liongard block. Pick one of its Presets, or set each area yourself: These always wait for a technician, whatever the preset: deleting an environment, and any write that sets a password, a secret or a token, such as a launchpoint’s secure configuration.

​
Raise a ticket for each new alert

A scheduled agent with Liongard’s Alerts & Change Detections set to Read Only and your PSA’s tickets set to Read / Write raises one ticket for each new Liongard alert: it reads the alerts raised since its last run, skips an alert that already has a ticket (the alert’s number, such as T20261022.00001, is in the ticket title), finds the client’s company in your PSA by the environment’s name, and raises the ticket with the finding and the action to take. In ServiceNow it raises an incident by default; say in the agent’s instructions when you want a request instead, and which assignment group, category and priority to set.
If Liongard already sends its alerts to your PSA through its own ticketing (in Liongard, Admin > Integrations > your PSA > Ticketing), say so in the agent’s instructions. The agent then raises no tickets of its own, and a triggered agent works the tickets Liongard raises.

​
Work a ticket an alert raised

An agent on a ticket raised from a Liongard alert finds the alert by its number, reads the system data behind it, and, when its instructions allow, runs the inspection again after the fix and resolves the ticket once Liongard closes the alert. Map each client’s environments on the Organization Mapping tab first: on a ticket, the agent reads only the environments mapped to the ticket’s company. See Liongard API for what the agent can read and change.