One of the most popular ways to leverage Liongard is to automate the system documentation when onboarding a new customer. The average MSP spends 40 hours on properly documenting a new customer. With Liongard, MSPs are onboarding new customers start to finish between 45 minutes and two hours.
Below is our suggested process for onboarding a new customer in Liongard. It is a four-step process:
- Step 1: Import and Integrate your New Customer
- Step 2: Roll out an On-Premises Agent
- Step 3: Activate your Auto-Discovered Inspectors
- Step 4: Roll out Additional Inspectors
Not Using an Integration?
If you are not using one of our Platform Integrations, you can add a new customer by navigating to Admin > Environments and selecting the Add Environment button. Here, please complete the fields and select Save to add the new customer.
Customers can also be bulk imported following the documentation found here.
For Integration best practices and complete details of our platform Integrations, please visit our Liongard Integration Best Practices document and the documentation for your specific Integration, linked within.
- In Liongard, navigate to Admin > Integrations > Select your Integration (left-hand menu) > Select Import & Mapping > Import Companies Tab
- Select the New customer (using the checkbox as shown in the screenshot below)> Actions > Import Companies, OR you can click the "+ Import" button at the bottom of the page.
- In the Map Companies Tab, make sure the new Environment is mapped correctly.
If you'd like to push this new customer's documentation from Liongard to IT Glue's Flexible Assets or ConnecWise's Configurations:
- In the Configuration Types > Select Environments Tab, ensure that the new customer's Environment's Auto-Updating toggle has been turned on
- In the Flexible Assets > Select Environments Tab, ensure that the applicable Flexible Assets/Configuration Types' Auto-Updating toggles have been turned on.
Data Landing in ConnectWise and IT Glue
As a reminder, Flexible Assets/Configurations will not land until the Inspector runs.
You can force run an Inspector by navigating to Admin > Inspectors > Click into an Inspector. Then, you can either bulk or single select the System Inspector > Actions > Run Inspectors, OR you can select the Play button next to a System Inspector.
If applicable, roll out an On-Premises Agent using our documentation.
- After installing the Agent, in Liongard, navigate to Admin > Inspectors. Here you will see a Windows Server Inspector running. This Inspector is associated to the Windows server that the Agent is installed on.
- After the Windows Server Inspector completes, if installed on a Domain Controller, an Active Directory Inspector will be auto-discovered.
- Additionally, when the Windows Server Inspector completes, it will auto-discover a Network Discovery Inspector.
- After the Network Discovery Inspector is activated and it completes its initial run, it will auto-discover several different Firewall Inspectors. A full list is included on the Network Discovery Inspector page.
You will activate this Active Directory Inspector and any additional Discovered Inspectors in Step 3.
For complete details of Liongard's Auto-Discovery, please visit our Auto-Discovery documentation.
- If you are taking advantage of a PSA Integration with Liongard, confirm that you have added the new customer's Company/Account into the PSA at least 24 hours before importing the customer into Liongard. If not, force run your applicable PSA Inspector. If you do not have a PSA Integration with Liongard, you will need to roll out an Internet Domain/DNS Inspector.
- If you are managing a system(s) for your new customer that has an associated Parent/Child Type Inspector, confirm that you have added the new customer’s tenant(s) to this system(s) in the last 24 hours. If you’ve added the new customer’s tenant(s) to this system(s) within the last 24 hours, then force run their applicable Parent/Child Type Inspector’s Parent Inspector(s). If you haven’t added the new customer’s tenant(s) to this system(s), then you will need to do so now, and then, force run their applicable Parent/Child Type Inspector’s Parent Inspector(s).
Parent/Child Type Inspectors:
- Azure Active Directory
- Bitdefender GravityZone
- Cisco Meraki
- Cisco Umbrella
- ConnectWise Automate
- Continuum RMM
- Datto BCDR
- Datto Networking
- Datto RMM
- Duo Security
- ESET Licensing
- Google Drive
- Google Workspace
- Kaseya VSA
- Microsoft 365
- Microsoft OneDrive
- Microsoft SharePoint
- Microsoft Teams
- N-able Backup
- N-able N-central
- N-able RMM
- Sophos Central
- Ubiquiti UniFi
- Veeam Availability Console
- Veeam Service Provider Console v4
- Webroot Secure Anywhere GSM
Navigate to your Dashboard > Select your new customer's Environment > Navigate to the Environment Admin tab (in the left sidebar) > Click the New Discovered Systems tab
Video isn't playing? Click here.
- Note: If you do not see Discovered Inspectors that you expect to see, navigate to Admin > Discoveries. Here you'll find all auto-discovered Inspectors across Environments in Liongard. Search for your expected auto-discovered Inspectors, and map them to your new customer Environment.
Bulk select the checkboxes to the left of the Discovered Inspectors > Actions > Activate Launchpoints
Use individual Inspector documentation to roll out Inspectors for the new customer's additional Systems.
Challenge: Race the Clock!
We have partners who are onboarding customers from 30 minutes to two hours. Think you can onboard a customer faster in Liongard?! Time it!
Because the majority of Liongard's Inspectors employ Auto-Discovery, rolling out System Inspectors in Liongard can be a quick task.
Updated 12 days ago