Liongard Roar

Roar Users Guide & Documentation

Welcome! You'll find comprehensive guides and documentation to help MSPs start working with Liongard's Roar as quickly as possible, as well as support if you get stuck. Let's go #MakeITRoar!

Get Started    

Roar Users Guide: Getting Started with Roar

Let's get you up and running with Roar!

You can always find your Onboard Checklist under Support > Show Onboard Checklist.

Step 1: Add Company Information

Fill out your company information under your Username > Company Settings.

Step 2: Add Users

Create Roar user accounts for anyone else on your team who will be rolling out Roar.
Admin > Users

Step 3: Import Companies

Import companies into Roar from ConnectWise Manage, IT Glue, Autotask, CSV, or manually one-by-one.

Helpful Docs
Setup Time

Mega Manual

Go to Roar > Environments > Add System

1 minute/customer

Step 4: Automate Documentation

Congrats! You're ready to attend a Roar Academy Webinar where you can learn about the platform, features and best practices.

Step 5: Roll out Roar Inspectors

Auto-Discovered Systems

Throughout your experience with Roar, you'll get to take advantage of a feature called auto-discovery. In short: our inspectors can discover other potential inspectors, which saves you a lot of manual setup work.

Here's an example of an auto-discovery chain.

Auto-discovers this...
Which auto-discovers this...

ConnectWise Manage and Autotask Integrations

Internet Domains

TLS/SSL certificates

Activate the inspectors for Internet Domains and TLS/SSL Certificates first.

Parent/Child Inspectors

For multi-tenant systems, Roar uses a concept called parent-child relationships. This is a version of auto-discovery that allows Roar to use one global parent inspector to auto-discover all the companies in your multi-tenant systems.

Setup the following parent/child inspectors in Roar next:

Time to Setup

15 minutes

10 minutes

5 minutes

10 minutes

10 minutes

These inspectors all run via Cloud agents, which are already in your instance and ready to go!

Step 6: Deploy an Agent

While many of our inspectors don't require privileged network access, some of them do. For those, we will need to install on-premise Roar Agents.

The most typical deployment strategy is to install one Roar Windows Agent per Environment with Inspectors that require local network access. A single Roar Agent can facilitate inspections across that whole network.

On-premise auto-discovery

Auto-discovers this...
Which auto-discovers this
Which auto-discovers this

A Windows agent installed on a domain controller

Windows inspector

Active Directory

Any other Windows Servers, SQL servers

Setup Firewalls


Sophos XG (preview)

Fortinet (preview)

WatchGuard (preview)

Getting Support

You can access support from the links right at the top-right of Roar.

Here are some quick links:

Roar Users Guide: Getting Started with Roar

Let's get you up and running with Roar!

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.