Overview 💥
Liongard automatically discovers, manages, and synchronizes ConnectWise PSA Configurations through its integration. When a Configuration is mapped to a Liongard-discovered asset, Liongard becomes the authoritative source of truth for that Configuration.
As a result, any manual changes made directly in ConnectWise PSA—such as renaming a Configuration—will be overwritten during the next Liongard inspection.
This article explains:
Why Configuration names and fields revert.
Which fields Liongard controls.
How mappings work and when they break.
How to intentionally unmap or remap an asset.
What happens when an asset is deleted in ConnectWise.
Best practices and when to contact support.
Why This Happens? 🤔
Liongard’s ConnectWise PSA integration follows a source-of-truth model.
This means:
Liongard discovers assets from integrated systems (servers, firewalls, cloud services, etc.).
Liongard writes those assets into ConnectWise Mapping as Configurations.
Liongard continuously synchronizes those Configurations so they reflect the actual discovered state.
When a Configuration is mapped:
Liongard owns the data for that Configuration.
ConnectWise PSA acts as the destination system.
Manual edits in ConnectWise are treated as temporary and are corrected on the next inspection.
What Liongard Controls? 🤨
Once a Configuration is mapped, Liongard overwrites changes made in ConnectWise during each inspection.
Fields Controlled by Liongard
Field Category | Examples | Behavior |
Configuration Name | Server01, FW-Main, M365 Tenant | Reverts to Liongard value |
Configuration Type | Server, Firewall, Cloud App | Reverts to Liongard value |
Mapped Custom Fields | OS Version, Serial Number, Model | Reverts to Liongard value |
Asset-Level Metadata | Description, Status | Reverts if mapped |
Key Rule:
✔ If the field is mapped → Liongard overwrites it
✔ If the field is unmapped → You may edit it freely in ConnectWise
How Do Mappings Work ? 🧐
A mapping is created when a Liongard Inspector discovers an asset and links it to a ConnectWise PSA Configuration.
Mapping Behavior Summary
Action | What Happens |
You manually rename the Configuration | Name reverts after the next inspection |
You edit mapped fields (OS, serial, model) | Values revert during sync |
You unmap the Configuration in Liongard | Full manual control is restored in ConnectWise |
You delete the Configuration in ConnectWise | Liongard recreates it on the next inspection |
You delete the asset in Liongard | Mapping clears; Configuration removed from CW on next sync |
How to Break or Change a Mapping 🧑🏫
✅ Option 1 — Disable Configuration Auto-Updating and Remove the Mapping (Recommended)
Use this option if you want to permanently manage the Configuration manually in ConnectWise.
Steps:
In Liongard, navigate to Integrations → ConnectWise PSA.
Go to Configuration Types.
Locate the Configuration by name or Inspector type.
Disable Configuration Auto-Updating for the specific Configuration.
Select Remove Mapping for that Configuration.
➡ After unmapping, Liongard stops controlling the Configuration, and you can safely rename or modify it in ConnectWise PSA.
✅ Option 2 — Delete the Configuration in ConnectWise PSA
If you delete a mapped Configuration directly in ConnectWise:
Liongard detects the missing asset.
Liongard clears the old mapping.
Liongard recreates the Configuration during the next inspection using Liongard-discovered values.
⚠️ Important: This option is not recommended unless your goal is to reset the asset entirely.
Troubleshooting: Why Did My Change Get Reverted? 👨💻
Symptom | Likely Cause | Resolution |
Configuration name keeps reverting | Asset is still mapped | Disable auto-updating and remove mapping |
Some fields revert, others don’t | Only mapped fields are controlled | Review field mappings in Liongard |
Configuration reappeared after deletion | Deletion triggered recreation | Disable auto-updating before deleting |
Duplicate Configurations appear | Manual asset created alongside Liongard asset | Remove the manual Configuration |
Mapping looks incorrect | Inspector mapped to wrong Configuration | Remove mapping and re-run inspection |
Best Practices 🤩
✔ Avoid manually renaming mapped Configurations in ConnectWise PSA.
✔ Disable Configuration Auto-Updating before unmapping an asset.
✔ Use Liongard naming conventions for consistency.
✔ Review mappings before deleting assets in ConnectWise.
✔ Allow Liongard inspections to complete after changes.
Mapping Workflow 🚀
Liongard Discovers Asset
↓
Liongard Maps Asset to ConnectWise Configuration
↓
Liongard Writes Name and Mapped Fields
↓
User Edits Configuration (Optional)
↓
Next Inspection Runs
↓
Liongard Overwrites Any Mapped Fields
Disclaimers ⚠️
Liongard supports one active ConnectWise PSA integration per platform instance.
Configuration behavior depends on mapping and auto-updating settings.
Unmapped fields are not controlled by Liongard and may be edited freely.
When to Contact Liongard Support 🦁
Contact Liongard Support if:
Mappings appear incorrect or inconsistent
Configurations are duplicated unexpectedly
Asset recreation is disrupting workflows
Unmapping does not behave as expected
You need guidance on naming conventions or restructuring Configurations
Please provide:
Environment name
Affected Configuration name(s)
Screenshot of the mapping section
Time of the last inspection
Summary 🌟
If a ConnectWise PSA Configuration is mapped to a Liongard asset, Liongard controls the name and mapped fields. Manual changes in ConnectWise will revert unless the mapping is intentionally removed and auto-updating is disabled.
Following the steps in this article ensures predictable behavior and avoids unwanted overwrites.