Overview

Lexful Inspector (Beta)

The Lexful Inspector monitors a Partner's Lexful IT documentation account. Run at the account level (the parent), it inventories every client organization, the asset-type schemas defined in the account, account-wide asset counts, the user and group roster, SSO connections, the IP restrictions list (IP allowlist), and tags. After the first parent run, Liongard auto-discovers one child inspector per organization; each child surfaces that Customer's per-type asset counts, asset records, contacts, and locations. The inspector is read-only. It counts and flags documentation, and never retrieves the contents of stored secrets or one-time codes. This is inspector behavior, not a read-only restriction on the API key.

Lexful is an AI-native IT documentation platform built specifically for MSPs (the Lexful platform has been generally available since February 2026). The Liongard Lexful Inspector is currently in Beta. It competes directly with IT Glue and Hudu, and ships Liongard as a day-one integration. A Lexful account belongs to one MSP and contains every managed client as an organization, each holding a flexible, user- and system-defined set of asset types (configurations, contacts, locations, documents, credentials, and more).

For Lexful-side setup, see Lexful's article: Inspect Lexful documentation with Liongard.

Inspector Setup Preparation

The credential setup happens in Lexful. You'll need administrator access and permission to create API keys under Platform > API keys. All three values Liongard needs (Account ID, Key ID, Secret) come from this one page.

1. Sign in to Lexful as an Admin and open Platform > API keys.
2. Select New key, enter a Name (we recommend "Liongard"), and select Create key.
3. Copy the Key ID and the Secret from the "Your API key is ready" dialog. The Secret is shown only once. If it's lost, create a new key.
4. Copy the Account ID from the bar above the key list (use the copy control). Liongard sends this as the X-Account-ID header on every request.

For more detail, see Lexful's guide: Create and manage API keys.

Liongard Inspector Setup

Lexful is a Parent/Child inspector — use the steps below for every Lexful integration. There is no individual/single-inspector setup path for this inspector.

Step 1: Parent Inspector Setup

Since Lexful is a multi-tenant system where a single account manages many client organizations, you will set up a single "Parent" Inspector with your Lexful account credentials, which will then auto-discover a "Child" Inspector for each organization.

In Liongard, navigate to Admin > Inspectors > Inspector Types > Navigate to the Lexful Inspector > Select Add System.

Fill in the following information:

• Type of Inspector: Parent
• Environment: Select your MSP's Environment
• Friendly Name: Suggested Naming: Environment Name [Lexful] Parent
• Agent: Select an On-Demand or Self-Managed agent
• Account ID: The Lexful Account ID from the bar above the key list on Platform > API keys
• API Key ID: The Key ID from the "Your API key is ready" dialog on Platform > API keys
• API Key Secret: The Secret shown once when the key was created
• API Base URL (advanced): Leave blank unless Lexful assigned your account a non-default regional host
• Inspector Version: Latest (Auto-Update)
• Scheduling: The Inspector will default to run once a day at the time the Inspector is set up. Here you can adjust the schedule.

Select Save. The Inspector will now be triggered to run within the minute.

Step 2: Child Inspector Setup

After the first run of the Parent Inspector, your Lexful organizations will be Auto-Discovered and surfaced on the Discovered Systems page. Each maps one-to-one to a Liongard Environment — including the Partner's own internal organization (Lexful's primary organization), which is discovered and flagged as primary rather than silently dropped, so you can choose whether to map it.

Navigate to the Discovered Systems tab in your Inspectors > Lexful page.

• Activate your Discovered Systems by ensuring they're mapped to the correct Environment > Select the checkbox to the left of Inspector(s) > Select the Actions drop-down menu > Activate Launchpoints.
• Users may also Archive Discovered Systems by selecting the checkbox to the left of the Inspector(s) > Select the Actions drop-down menu > Archive Launchpoints.

Troubleshooting

• A Parent run fails immediately — the Account ID, Key ID, or Secret is incorrect, or the key was revoked; re-copy the Account ID from the bar above the key list on Platform > API keys and create a new key there.
• A Parent run fails even though the credentials are correct — if IP restrictions are switched on in Lexful, confirm the IP address of the selected Agent (On-Demand or Self-Managed) has been added to the list.
• SSO Connections, Allowed IPs, or Auth Methods data is empty — the API key's role may lack permission for that account-administration surface, or none are configured; the inspector treats these as optional and continues.
• A child organization shows zero assets — that organization may have asset management disabled in Lexful, or it genuinely has no documented assets yet.
• A child launchpoint did not appear — child launchpoints are discovered only after the first successful parent run; confirm the parent ran, then check the Discovered Systems tab.