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    

Getting Started with Roar

Let's get you up and running with Roar!

You can always turn on your Onboard Checklist on your Roar Dashboard under Support > Show Onboard Checklist.

Step 1: Add Company Information

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

Video isn't playing? Click here.

Step 2: Add Users

Create Roar User Accounts for anyone else on your team who will be rolling out Roar under
Admin > Users.

Video isn't playing? Click here.

Step 3: Import Companies

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

Integrating a PSA

If you choose to integrate your PSA with Roar, Roar will auto-discover all of the Internet Domain/DNS Inspectors for the applicable companies selected in your Import Options.

For more information on integrations, please visit our Roar Integration Best Practices documentation

System
How-to Video
Helpful Docs
Setup Time

Manually

In Roar, go to: Admin > Environments > Add Environment

1 minute/customer

Step 4: Automate Documentation

Video isn't playing? Click here.

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

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.

Video isn't playing? Click here.

Here's an example of an Auto-Discovery chain:

This...
Auto-Discovers...
Which Auto-Discovers...

ConnectWise Manage and Autotask Integrations

Internet Domains

TLS/SSL Certificates

Note: In the App, you can see which Inspectors Auto-Discover other Inspectors and which Inspectors are Parent/Child Type Inspectors by navigating to Admin > Inspectors > Discovers column.

As a best practice, 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:

Inspector
Time to Setup

10 minutes

5 minutes

5 minutes

5 minutes

5 minutes

5 minutes

15 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.

Video isn't playing? Click here.

With systems that require local network access, the most typical deployment strategy is to install one Roar Windows Agent per Environment. A single Roar Agent can facilitate inspections across that whole network.

On-Premise Auto-Discovery

This...
Auto-Discovers...
Which Auto-Discovers...
Which Auto-Discovers...

A Windows Agent installed on a domain controller

Windows Inspector

Active Directory

Any other Windows servers, SQL servers, & Hyper-V

Setup Firewalls

Next, we recommend setting up your firewall Inspectors.

System

Sophos XG (preview)

WatchGuard (preview)

Getting Support

You can access support right from your Roar Instance! In the top right corner of your instance, there is a Support drop down menu. There you will find three quick links to our Documentation Site, a link to Create a Support Ticket, and a link to Support a Feature Request.

Please see below for some quick links:

Last Updated: 2019-10-11

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.