Liongard Integration Setup Guide

Liongard connects to Scopable with a read-only access key pair. You paste your instance slug and key pair into Scopable, map each Liongard environment to the matching Scopable client, and Scopable syncs that environment intelligence onto the client record where quoting, reviews, and Co-Work can use it.

Liongard is an enrichment source, not a system of record. Scopable never creates clients from Liongard environments. You decide which environment belongs to which client, and that explicit mapping is what keeps vendor environment names from turning into accidental CRM records.

Step 1: Get your Liongard credentials

In Liongard:

1. Sign in to your Liongard instance and note the instance slug in your address bar. If you log in at https://acme.app.liongard.com, your slug is acme.
2. Create or open an API access key and copy both the Access Key ID and the Access Key Secret.

Scopable only ever reads from Liongard. It requests environments, systems, inventory, detections, and timeline records. It does not create, change, or delete anything in your Liongard instance.

Keep the Access Key Secret handy. Liongard shows it once, and Scopable stores it encrypted without ever displaying it again.

Step 2: Open the Liongard integration in Scopable

1. Log in to Scopable as an Admin.
2. Click Integrations in the left-side navigation under Administration.
3. Open the Liongard tab.

Step 3: Connect and test

The Liongard card asks for three values:

• Instance slug: just the slug, not a URL. Scopable appends .app.liongard.com for you and shows that suffix beside the field. Use lowercase letters, numbers, and single hyphens. Pasting a full URL is rejected with "Enter only the instance slug, not a URL."
• Access Key ID: from Step 1.
• Access Key Secret: from Step 1. Stored encrypted in Scopable's secure vault and never returned to the browser.

Click Save & Test Connection. Scopable saves the credentials and immediately runs a connection probe against Liongard. On success you see a Connected badge and a "Liongard answered the connection probe" confirmation.

Once connected, the card shows your Instance, Base URL, and a redacted Access key hint, plus a status row with Status, Last tested, Last success, and the number of Environments Liongard reported.

Three buttons stay available:

Step 4: Map Liongard environments to clients

Liongard environments are mapped on the shared Mappings page, alongside every other connected source. From the Liongard tab, use Open Mappings, or go to Integrations to Mappings directly.

1. Click Refresh matches. This pulls the current environment list from Liongard and runs it through Scopable's matcher.
2. Review the Liongard column. Each cell is in one of three states:
   • Confirmed: the environment is mapped to that client and is eligible to sync.
   • Suggested: Scopable found a likely match and shows its confidence. Accept it to confirm the mapping.
   • Unmatched: no mapping yet. Pick the right client, or leave it unmapped.
3. Use the Search field ("Client or external org") to find a specific client or environment in a long list.
4. Clear a mapping from its cell if you linked the wrong client.

Only environments with an active confirmed or auto-linked mapping sync. Unmapped, skipped, conflicted, and errored environments are counted as skipped and no data is imported for them.

No clients yet? Scopable will not invent them. Create the clients first, then come back and map. This is deliberate: it keeps your client list under your control rather than Liongard's.

Step 5: Run and monitor sync

Back on the Liongard tab, the Sync status card is your control panel.

• Run sync starts a sync immediately for every mapped environment.
• Scopable also runs a scheduled sync daily for accounts with an active connection, so you do not have to run it by hand.
• The summary row shows Mapped, Skipped, and Last run.
• The table breaks results out by entity: Systems, Assets, Metrics, Detections, and Timeline. Each row shows its status, records updated, records skipped, records errored, and when it last synced.

Entity status reads as Synced, Running, Idle, or Needs attention.

Sync is resilient by design. If one entity fails, the ones that succeeded still save, and the previous data for the failed entity is kept rather than wiped. A partial run reports "Some provider calls failed; prior data was preserved." Run it again once Liongard is responding normally.

Step 6: Use Liongard data in Co-Work

Once Liongard is connected and at least one environment is mapped, Co-Work can answer client questions from the synced Liongard data. Try prompts like:

• "Summarize this client's Liongard health."
• "Find inventory signals for this client."
• "List recent detections for this client."

Co-Work reads the summaries Scopable synced and owns. It does not hold your Liongard credentials, and it has no direct access to the Liongard API. Answers include the source timestamp so you can see how fresh the data is, and Co-Work flags stale or missing sync data rather than presenting it as current.

Co-Work only offers these abilities when the integration is connected, credentials are active, and a mapping exists. Before that, it will tell you the data is not available instead of guessing.

Troubleshooting

The Liongard tab is not there

Liongard is available to every Scopable account, but the tab only appears for users who can manage integrations. If you cannot see it, ask an administrator on your account to grant you integration-management permission, or to run the setup for you.

The connection test fails on credentials

Scopable reports "Rotate the access key pair and test again." The Access Key ID or Secret is wrong, expired, or revoked. Generate a fresh pair in Liongard, click Reconfigure, and enter both values again with no trailing spaces.

The connection test fails on the instance

Scopable reports "Check the Liongard instance slug." The slug does not resolve to a Liongard instance. Confirm the value against your Liongard login URL, and enter only the slug, not the whole address.

The connection test hits a rate limit

Scopable reports "Wait for the rate-limit window, then test again." Liongard is throttling requests. Wait for the window to clear, then test again. Nothing is lost.

Liongard is timing out or unavailable

Scopable reports "Try again after Liongard responds normally." This is a Liongard-side availability or timeout condition, not a credential problem. Your saved settings are untouched. Retry once Liongard is healthy.

My environments are not syncing

Check the mapping first. An environment only syncs when it has an active mapping to a client. Open Mappings, click Refresh matches, and confirm the environment shows as Confirmed rather than Unmatched or skipped. The Skipped count on the Sync status card tells you how many environments are being passed over.

The environment list is empty or out of date

Click Refresh matches on the Mappings page. That is the action that fetches the current environment list from Liongard. Opening a Liongard mapping dropdown also refreshes the list once per page session.

I rotated my Liongard access key

Click Reconfigure on the Liongard tab, enter the new Access Key ID and Secret, and save. Scopable tests the new pair immediately. Your environment mappings and synced data are preserved through a key rotation.

Still stuck?

Email us at [email protected] with a screenshot of the error and we will help you get connected.

Frequently Asked Questions

Does connecting Liongard let Scopable change anything in my Liongard instance?

No. The integration is read-only. Scopable reads environments, systems, inventory, detections, and timeline records. It never creates, edits, or deletes anything in Liongard.

Does Scopable create clients from my Liongard environments?

No, and this is deliberate. Liongard is an enrichment source. You map each environment to a client you already have in Scopable. Environments you never map simply do not sync.

How often does sync run?

Scopable runs a scheduled sync daily for accounts with an active connection. You can also run one on demand with Run sync on the Liongard tab.

Where is my Access Key Secret stored?

Encrypted in Scopable's secure vault. It is never shown in the interface after you enter it and is never sent to your browser. Disconnecting removes it.

What happens to my data if I disconnect?

Disconnecting removes the stored access key pair. Sync stops, since there are no credentials to call Liongard with. Reconnect later with a new key pair to resume.

Why does one entity say "Needs attention" while the others synced?

Sync handles each entity separately so one provider failure does not cost you the whole run. The entities that succeeded are saved, and the failed one keeps its previous data instead of being emptied. Run the sync again once Liongard is responding.

Will this conflict with my PSA or RMM?

No. Liongard runs alongside your PSA and RMM. It adds environment intelligence to the client record rather than competing for ownership of it.