Device Management

Liongard

Bring Liongard ROAR automated documentation into Dex - browse environments, systems, launchpoints, and agents in plain language.

Dex connects to the Liongard ROAR API so you can explore your automated documentation conversationally. Read-only by design: look up a customer Environment, list the systems, launchpoints, and agents captured for it, and run read-only Environment dashboard queries. Liongard is an MSP global app - one shared Access Key ID and Secret spans your whole instance, and each Dex tenant is confined to its own Liongard Environment via environment_id, so every customer sees only its own documentation.

Start free →See Dex Live

What Dex does with Liongard

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

List every Liongard Environment from the MSP-master connection to map customers to their environment_id
Read one Liongard Environment by id, path-forced to this tenant on a scoped connection
List the systems captured for an Environment, with environmentId forced on a scoped connection
List the launchpoints configured for an Environment
List the agents reporting for an Environment
Run read-only Environment dashboard queries via the v2 query endpoint
Deploy as an MSP global app - one Access Key ID and Secret, each customer confined to its Liongard Environment via environment_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List every Liongard Environment so I can find the one for Contoso
>Show me the Environment details for environment_id 142
>What systems does Liongard have documented for this customer?
>List the launchpoints configured for this Environment
>Which agents are reporting for this Environment right now?
>Run a read-only dashboard query against this Environment

Policy actions

Every action Dex can take on Liongard is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`liongard_list_environments`	List every Liongard Environment (master connection only; disabled on a scoped child)	—
`liongard_get_environment`	Read one Liongard Environment by id (path-forced on a scoped child)	—
`liongard_list_systems`	List Liongard systems for this Environment (environmentId forced on a scoped child)	—
`liongard_list_launchpoints`	List Liongard launchpoints for this Environment	—
`liongard_list_agents`	List Liongard agents for this Environment	—
`liongard_environment_query`	Run read-only Environment dashboard queries (v2; path-forced on a scoped child)	—

How to configure Liongard

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Liongard, go to Admin > Access Keys (or Account Settings) and create an Access Key for Dex.
2
Copy the Access Key ID and the Access Key Secret shown once at creation - regenerate if the Secret is lost.
3
Note your Liongard subdomain (e.g. us1 for https://us1.app.liongard.com).
4
In Dex, enable the Liongard integration and paste the Access Key ID, Access Key Secret, and instance subdomain. Leave environment_id blank on the MSP-master connection.
5
Dex validates the credentials with a live read before saving, then discovery maps each tenant to its Liongard Environment via environment_id.

Credentials required

access_key_id: Liongard Access Key ID (secret - never surfaced back)
access_key_secret: Liongard Access Key Secret shown once when the key was created
instance: Liongard subdomain only, e.g. us1 for https://us1.app.liongard.com
environment_id: This tenant's numeric Liongard Environment id - leave blank on the MSP-master connection, set it on each tenant connection once discovered

Requirements

•A Liongard instance with an Access Key ID and Secret created under Admin > Access Keys
•Read-only by design - Dex browses environments, systems, launchpoints, and agents but does not modify them
•The MSP-master connection (blank environment_id) can list every Environment; a scoped child connection is confined to its own Environment
•For MSPs, deploy as a global app with per-tenant Environment scoping via environment_id