Once you've set up Liongard's Kaseya BMS integration and Imported and mapped Accounts from Kaseya BMS, you're ready to enable ticket creation in your PSA.

Step 1: Enable Kaseya BMS Service Ticket Generation

Navigate to Admin > Integrations > Kaseya BMS > Ticketing and select Enable Kaseya BMS Service Ticket Creation

Step 2: Configure Ticket Details

Configure how tickets will land in your Kaseya BMS instance by customizing the parameters below the Enable Checkbox.

Here are some recommended defaults, but you should customize them to fit your Kaseya BMS workflow:

• Ticket Type: Incident
• Default Ticket Queue: Level One Support
• Generate a Test Ticket: Log in to your Kaseya BMS instance to view the ticket.

📘

Sending Tickets to Specific Kaseya BMS Queues

You can send Liongard Tickets to specific Kaseya BMS Queues.

Step 3: Configure Ticket Statuses and Priorities

Liongard has an internal set of Status and Priority fields associated with Actionable Alerts in Liongard. With the Status Mapping and Priority Mapping sections, you can map those internal Liongard values to equivalent values in your Kaseya BMS instance.

Statuses

When a ticket is first created, Liongard sets the Status field to the Kaseya BMS status mapped to the "New" status in Liongard.

Prior to an inspection processing, Liongard will retrieve the latest status for each Liongard-created Kaseya BMS ticket and will update the matching Actionable Alert status in Liongard. This allows for consistent management of Liongard-created Kaseya BMS tickets and Liongard Actionable Alerts.

For this sync to work properly, each ticket status must be mapped on the Admin > Integrations screen using the "Select Additional PSA Status" pull-down, as detailed below.

This feature is enabled by default and can be disabled on the Admin > Integrations > PSA > Ticketing screen.

You should have Kaseya BMS statuses for the following Liongard Task statuses:

• New
• Re-Opened
• Closed - Complete
  • Tickets set to this status will trigger a validation.
• Silenced
  • This is the status Liongard will use if an Actionable Alert is silenced

Note: Liongard's "Closed-Complete" status will trigger a revalidation and possible reopening of the ticket, or if another Status is mapped to Closed within Kaseya BMS, it will also trigger a self-heal attempt (revalidation) and possible reopening.

If Liongard detects that a condition is resolved, it will automatically close the ticket in Kaseya BMS.

Priorities

Liongard has an internal set of Priority values that are set by Actionable Alert rules. You can choose to map those Priorities to the preferred priorities you use in Kaseya BMS.

To set up which alerts you want sent as tickets, click here.

Additional PSA Statuses

Any status in your PSA can be mapped in Liongard. Clicking the Select Additional PSA Status button on the ticketing page will allow you to select the status you would like to map.