Overview 💥
Liongard integrates with ConnectWise PSA (formerly Manage) to automatically map discovered assets and data from specific Liongard Inspectors to corresponding ConnectWise Configuration Types. Understanding these mappings is essential for:
Validating data flow between Liongard and ConnectWise PSA.
Troubleshooting missing or unexpected configuration data.
Auditing how Inspectors align with ConnectWise configuration structures.
This article explains where to view these mappings, what each column represents, and what to do if something doesn’t look right.
Why This Matters? 🤔
Each Liongard Inspector is designed to collect a specific set of data (for example, Microsoft 365, Active Directory, firewalls, or backup systems). That data is then mapped to a specific Configuration Type in ConnectWise PSA.
If mappings are misunderstood or misconfigured:
Data may appear under an unexpected Configuration Type
Assets may appear duplicated or missing
Reporting and automation downstream may be impacted
Having visibility into Inspector-to-Configuration mappings helps ensure data accuracy and consistency across platforms.
How to View Inspector-to-Configuration Mappings? 🧐
Follow the steps below in the Liongard platform:
Navigate to Admin
Select Integrations
Choose ConnectWise PSA
Open the Configuration Types tab
Review the mapping table
Understanding the Mapping Columns 🧑🏫
The following columns provide visibility into how Inspectors and ConnectWise PSA are linked:
Column Name | Description |
Liongard Inspector(s) | Displays the Liongard Inspector or Inspectors responsible for populating data into the mapped Configuration Type. Multiple Inspectors may appear if more than one contributes data. |
Mapped ConnectWise Configuration Type | Shows the ConnectWise PSA Configuration Type that receives data from the associated Liongard Inspector(s). |
These columns define the authoritative relationship between Liongard discovery and ConnectWise PSA asset records.
Tips for Working With the Mapping List 📝
✅ Search and Filter
Use search or filtering options to quickly locate:
A specific Inspector
A specific Configuration Type
This is especially useful in environments with a large number of integrations.
✅ Export for Auditing
Exporting integration mapping data can be useful for documentation or audit purposes. It can be used for:
Internal reviews.
Change management documentation.
Partner or customer reporting.
Troubleshooting Common Mapping Questions 👨💻
✅ A Mapping Looks Incorrect or Is Missing
If an Inspector does not appear mapped as expected:
Confirm the Inspector has successfully run at least once.
Verify the ConnectWise integration is healthy and authenticated.
Check that the Inspector is enabled and assigned to the correct environment.
Re-run the Inspector and allow time for synchronization.
✅ Unexpected Configuration Types Receiving Data
This typically indicates:
A default mapping applied by the integration.
Historical mappings that were not intentionally changed.
Review the Configuration Types list carefully to confirm which Inspector owns the data.
Best Practices 🤩
Avoid manually changing Configuration Types in ConnectWise without understanding the Liongard mapping
Review Inspector mappings after adding new Inspectors or integrations
Use Liongard as the source of truth for Inspector-driven asset data
When to Contact Support 🦁
Contact Liongard Support if:
Inspector mappings appear incorrect and cannot be resolved through re-syncing
Expected Inspectors do not appear in the Configuration Types list
Data is consistently landing in the wrong ConnectWise Configuration Type
When reaching out, include:
The affected Inspector name
The expected and actual Configuration Type
Screenshots of the Configuration Types mapping screen (if possible)
Disclaimer ‼️
UI labels and layout may vary slightly depending on platform updates
Third-party platform behavior (ConnectWise PSA) is subject to change outside of Liongard’s control