Skip to main content
This guide walks you through connecting your Liongard instance to MSPortal.ai. Liongard is a configuration audit platform that continuously inspects your clients’ IT environments. By integrating with MSPortal.ai, you can map Liongard metrics directly to compliance checks, bridging automated configuration audits with your compliance reporting workflow. Connecting Liongard imports its data for MSP staff workflows. It does not share Liongard data with your clients or prove that a compliance check has passed.

​
Overview

The Liongard integration syncs configuration audit data into MSPortal, allowing you to:
  • Import environments, systems, and inspectors from Liongard
  • Sync configuration metrics and their current values across all clients
  • Track security detections and anomalies
  • View per-device Liongard data directly in the Device Detail panel with pass/fail/warning metrics and change history
  • Map individual metrics to MSPortal compliance checks for automated audit evidence
The compliance metric mapping feature is what makes this integration especially powerful. Instead of manually assessing compliance checks, you can link them to live Liongard metrics that update automatically with every inspection cycle.
The Liongard integration is currently in Beta. Core functionality is complete and available for all users. You will see a “Beta” badge on Liongard in the Integrations page.

​
Prerequisites

Before you begin, ensure you have:
  • Active Liongard account with API access
  • MSPortal.ai account with integration management permissions
  • Companies already set up in MSPortal (from your PSA integration or manually created)
The Liongard integration matches environments to companies in MSPortal. Import your companies from your PSA integration first, or create them manually, so you can match environments to existing companies.

​
Part 1: Generate API Credentials in Liongard

Before connecting to MSPortal.ai, you need to create API credentials in your Liongard instance.
1

Log into Liongard

Access your Liongard Roar instance. Common instance names include region codes like us1, us2, ca1, eu1, but your instance may also have a custom name (e.g., safari). Your instance name is the subdomain in your Liongard URL:Check your browser’s address bar when logged into Liongard to find your instance name.
2

Navigate to Access Keys

In the Liongard dashboard, go to Admin > API > Access Keys.
3

Create an Access Token

Click Create. Set the Expiration Date to Unlimited, then click Generate.
Copy both the Access Key and Access Key Secret immediately! These are only shown once and cannot be retrieved after you leave this page. Store both values securely for use in MSPortal.ai.
4

Note Your Roar Instance Name

Identify your Liongard Roar instance name. This is the subdomain visible in your browser’s address bar when logged into Liongard (e.g., us1, ca1, or a custom name like safari). You will need this when connecting in MSPortal.

​
Required Information

Before proceeding to MSPortal, ensure you have the following:

​
Part 2: Connect in MSPortal

Go to Settings > Integrations, open the Directory tab, find Liongard, and select Connect. If Liongard is already connected, open it from the Active tab with Open instead. The connection page lists its tasks in the Setup guide. Under Setup you will find Connect, Choose data, Import or match companies, Import devices, and Review. Under Manage you will find Overview and Sync activity. Select a task to open it.

​
Connect

1

Enter Instance URL

In Instance URL, enter your Liongard Roar instance name. You can enter either:
  • Just the instance name (e.g., us1, ca1, safari)
  • The full URL (e.g., https://us1.app.liongard.com)
MSPortal will automatically resolve the full URL if you enter only the instance name. Your instance name is the subdomain in your Liongard URL (e.g., the us1 in https://us1.app.liongard.com or safari in https://safari.app.liongard.com).
2

Enter API Credentials

Fill in the following fields:
Credentials are stored in the vault and never shown again. They are never exposed in logs or API responses.
Liongard Instance URL, Access Key ID and Access Key Secret fields

The Connect task's Instance URL, Access Key ID and Access Key Secret fields.

3

Test Connection

Select Test connection to verify your credentials. You’ll see Connection verified when the test passes. Testing does not save the integration.If the connection fails:
  • Verify your Instance URL matches your Liongard instance exactly
  • Check that your Access Key ID and Access Key Secret are copied correctly without extra spaces
  • Ensure the API key has not been revoked or expired
  • Confirm your Liongard account has API access enabled
4

Save and Continue

Once the connection test passes, select Save and continue to save your credentials. MSPortal starts fetching your environments in the background. Allow that work to finish before you expect every environment to appear.

​
Import or match companies

Match Liongard environments to your MSPortal companies. This determines which audit data syncs to which company. The workspace is titled Import or match Liongard environments.
1

Wait for Environments

After you save the connection, MSPortal begins syncing your environments from Liongard. This may take a few minutes depending on the number of environments.
If no environments appear, wait a few minutes and check back. If they still don’t appear, select Sync environments in the empty list or Run sync in the connection header, then check Sync activity.
2

Review Suggested Matches

Open Suggested to see environments MSPortal matched to companies by name. Select Accept to save a suggestion, or Change to pick a different company. Accept N strong matches accepts every suggestion with 90% confidence or more at once.Review suggestions before you accept them. Similar names do not always mean two records belong to the same client.
3

Match Remaining Environments

In Import, the view the workspace opens on, choose the correct MSPortal company for each environment. If the company does not exist yet, select Import company to create it and match it in one step. Use existing companies where possible.Select Ignore for environments you don’t need. You can find them under Ignored and Restore them later.
4

Check Your Matches

Review Matched. Choosing a company or accepting a suggestion saves the match immediately, and a company you create here is saved right away. Wait for each save to finish before you rely on the link.Remove match clears the saved link immediately. It does not delete the Liongard environment or the MSPortal company.
Only data from matched environments will sync to MSPortal. You can return to match more environments at any time.

​
Choose data

Choose data comes before Import or match companies in the Setup guide, but it only fills in once you have matched environments. It shows what has synced for your matched environments. There are no separate switches per data type; everything below syncs for matched environments. If nothing has synced yet, match environments, then select Sync all data. The sync runs in the background and may take several minutes; the counts update as data arrives. If the counts stay at zero, check your matches and connection rather than starting more syncs. This task is optional. It counts as done once systems have synced for a matched environment.

​
Import devices

Use Import devices to bring Liongard systems into your MSPortal device inventory. Under Match device types, choose the device type each Liongard type becomes, or use Match all suggested or Match the rest with AI. Turn on Auto-import for types you want imported automatically, then use Import all matched to import the staged devices. Every change saves immediately. See Import Devices.

​
Review

Open Review and select Finish setup once the required tasks are done. Finishing setup does not wait for all Liongard data to finish syncing. Check the counts in Choose data and the results in Sync activity before you rely on the data.

​
Part 3: Map Metrics to Compliance Checks

This is the key feature of the Liongard integration. After the initial sync completes, you can map individual Liongard metrics to MSPortal compliance checks with custom evaluation rules, creating a direct link between automated configuration audits and your compliance reporting.

​
Accessing the Metrics Page

Navigate to Settings > Compliance > Metrics. This dedicated tab shows all synced metrics from your Liongard instance with options to browse by metric or by device.
For the full guide on creating compliance checks from metrics, custom rule evaluation, and how the auto-sync works with compliance runs, see Liongard Compliance Metrics.

​
Quick Start

1

Browse Metrics

Go to Settings > Compliance > Metrics to see all synced configuration audit data from Liongard. Use the Per Metric or Per Device tabs to find what you need.
2

Create a Compliance Check

Click any metric row, then click Create Compliance Check in the detail panel. Choose to use Liongard’s native status or define custom rules with thresholds.
3

Add to a Compliance Run

Add the metric-linked check to a compliance run (directly or through a group). The sync will keep the assignment status current for active runs.

​
Why Map Metrics to Compliance Checks?

Automated Evidence

Liongard metrics provide continuous, automated evidence for compliance checks. No more manual assessments for configuration-based requirements.

Custom Rules

Define threshold-based rules like “fail if password length is below 12” instead of relying on Liongard’s native pass/fail.

Per-Device Tracking

Each device gets its own compliance status based on its individual metric value, not a company-wide average.

Historical Snapshots

Completed compliance runs freeze as point-in-time snapshots. Start a new run to track ongoing changes.

​
What Gets Synced

​
Part 4: Liongard Data on Devices

Once Liongard environments are matched and data is synced, you can view Liongard configuration audit data directly on individual devices in the Devices module.

​
Accessing the Liongard Tab

1

Open a Device

Navigate to Devices and click on any device to open the Device Detail panel.
2

Select the Liongard Tab

If Liongard has data for this device, a Liongard tab appears in the detail panel. Click it to view the device’s configuration audit data.
The Liongard tab only appears for devices that Liongard has inspected. MSPortal automatically matches devices to Liongard systems by name, IP address, or MAC address.

​
What You See

The Liongard tab displays three main sections:

​
Summary Cards

At the top, summary cards show the overall health of the device’s configuration metrics:
  • Passing - Number of metrics with a passing status (green)
  • Failing - Number of metrics with a failing status (red)
  • Warning - Number of metrics with a warning status (orange)
Click any summary card to filter the metrics list to only that status.

​
System Overview

Shows the Liongard system name, environment, inspector type, and when the device was last inspected.

​
Configuration Metrics

Metrics are organized into two collapsible sections: Each metric row shows the metric name, current value, and pass/fail/warning status. Click a metric to expand it and see the previous value for comparison. Use the search bar to filter metrics by name or value. Click Expand/Collapse to toggle all metric details at once.

​
Recent Changes

The Recent Changes section shows configuration change detections from Liongard. Each entry shows:
  • The change description and inspector name
  • When the change was detected
  • A diff view showing what was added (+) or removed (-) in the configuration
Click any detection to expand and see the full change diff.

​
How Device Matching Works

MSPortal automatically matches your imported devices to Liongard systems using multiple strategies:
  1. Direct link - If the device was previously matched, it uses the stored link
  2. Name match - Matches by device hostname or name within the same company
  3. IP/MAC fallback - If no name match is found, attempts to match by IP address or MAC address
Once matched, the link is saved so future lookups are instant.

​
Managing Your Integration

After setup, open the Liongard connection from the Active tab in Settings > Integrations. Select any task in the Setup guide to return to it. Disconnect… removes the stored credentials, the matches between Liongard environments and companies, and synced data.

​
Checking or Replacing API Credentials

1

Open Connect

Open the Liongard connection and select Connect in the Setup guide.
2

Retest the Saved Credentials

The saved credentials are read-only. Select Test connection to check them again.
3

Replace a Key

Credentials for an existing Liongard connection cannot be changed on this page yet. To use different credentials, disconnect and connect again. Disconnecting also removes your environment matches and synced data, so contact support@msportal.ai first if you want help, and don’t revoke the working key in Liongard until the new connection works.

​
Troubleshooting

Causes:
  • Incorrect Roar instance name, Access Key ID, or Access Key Secret
  • API key has been revoked or expired
  • Liongard account does not have API access enabled
Solutions:
  1. Verify your Roar instance name matches exactly what appears in your Liongard URL (e.g., us1, ca1, or your custom name)
  2. Check that your Access Key ID and Access Key Secret are copied exactly, without extra spaces
  3. Generate a new access token in Liongard (Admin > API > Access Keys) if the current one is expired
  4. Confirm your Liongard account has API access permissions
No. Test connection only checks the credentials. Select Save and continue to save a new connection, then check environment discovery and synced data separately.
Causes:
  • Initial sync still in progress
  • API key lacks read permissions
Solutions:
  1. Wait a few minutes for the background sync to complete
  2. Use Run sync in the connection header, then check Sync activity
  3. Verify your API key has the necessary read permissions in Liongard
Causes:
  • Metrics sync not yet complete
  • No environments have been matched to companies
Solutions:
  1. Ensure at least one environment is matched to a company
  2. Wait for the metrics sync to complete (this may take several minutes after initial setup)
  3. Check the Metrics and Metric values counts in Choose data, and select Sync all data if they are zero
Causes:
  • Metric is not properly mapped to a compliance check
  • Metric values have not synced yet
  • The compliance check was created after the last sync
Solutions:
  1. Navigate to the Metrics page and verify the mapping is in place
  2. Wait for the next sync cycle to update metric values
  3. Use Run sync on the Liongard connection if needed
Causes:
  • Environment is not matched to a company
  • Inspectors are not configured for that environment in Liongard
Solutions:
  1. Match the environment to a company in Import or match companies
  2. Verify that the environment has active inspectors configured in Liongard
No. Remove match clears that link immediately. Match the environment again if the removal was unintended.
No. It completes the setup flow, while sync work can continue in the background. Verify relevant records, company matches and timestamps before using them.
No. Connecting and importing do not share Liongard data with company users. Set inspector and system sharing in Settings > Documentation under the Liongard tab, then verify access with the intended company user.

​
Best Practices

Match Environments First

Always match your Liongard environments to companies before expecting data to flow. Only matched environment data syncs to MSPortal.

Start With Strong Matches

Use Accept N strong matches for environment matching, then review the rest one by one. It saves significant time with large environment lists.

Prioritize Key Metrics

Focus your compliance metric mappings on high-value checks first, such as MFA status, backup verification, and firewall configuration metrics.

Review Regularly

Periodically review the Metrics page to map newly discovered metrics as Liongard adds inspectors or your clients’ environments change.

​
Security and Privacy

  • Credential Storage: Your Liongard API credentials are encrypted using vault storage and never exposed in logs or responses
  • Data Isolation: All synced data is tenant-isolated and only visible to your organization
  • Read-Only Access: MSPortal only requires read access to Liongard data; it never modifies your Liongard configuration
  • Client Visibility Is Separate: Connecting Liongard does not share its data with company users. Set inspector and system sharing in Settings > Documentation under the Liongard tab

​
Need Help?

For assistance with the Liongard integration, contact support@msportal.ai.