> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect your Kaseya VSA X (VSAX) RMM to Neo Agent for device, asset, and automation context

## Setup Overview

Setting up the Kaseya VSA X integration involves two main steps:

<CardGroup cols={2}>
  <Card title="Creating an API Token" icon="key" href="/integrations/rmm/vsax/creating-api-key">
    Create a Third-Party Token in your VSA X portal with the scopes Neo Agent needs.
  </Card>

  <Card title="Connecting to Neo Agent" icon="link" href="/integrations/rmm/vsax/connecting-to-neo">
    Configure the connection between your VSA X tenant and Neo Agent using your Token ID and Token Secret.
  </Card>
</CardGroup>

## Prerequisites

Before starting the integration setup, ensure you have:

* **Admin Access**: An account in your VSA X tenant with the **API Access** permission (Super Admin, or a custom role that includes it)
* **Your tenant URL**: e.g. `https://yourtenant.vsax.net`

<Info>
  Kaseya VSA X (also written **VSAX**) is the modern, cloud-native Kaseya RMM built on the Pulseway engine — distinct from the classic VSA 9/10. Its REST API v3 lives at `https://<tenant>.vsax.net/api/v3`.
</Info>

## What Neo Can Do with VSA X

Neo Agent reads and (where you allow it) writes the VSA X REST API v3 surface, gated by per-area permission groups you configure in Agent Settings.

<AccordionGroup>
  <Accordion title="Devices">
    * **Device lookup** — find devices, status, OS type, organization/site/group, applied policies, antivirus status
    * **Custom fields & notifications** — read device custom fields and notifications
    * **Write** — move a device to another group, update device custom fields
  </Accordion>

  <Accordion title="Assets (hardware & software inventory)">
    * **Hardware inventory** — BIOS, operating system, CPU, RAM, disks, network adapters
    * **Installed software** — name, publisher, version per device
    * **Last-seen** — the true `LastSeenOnline` timestamp

    <Info>
      The assets endpoint is rate-limited by Kaseya to 60 requests/hour, so Neo queries it sparingly.
    </Info>
  </Accordion>

  <Accordion title="Organizations, Sites, Groups">
    * **Hierarchy** — read and (with write access) manage the organization → site → group structure and their custom fields
  </Accordion>

  <Accordion title="Automation">
    * **Catalog** — list automation scripts, tasks, and workflows and inspect execution history
    * **Execute** — run pre-registered scripts on a device and read back the result (with write access to the Automation group)

    <Info>
      Script execution runs scripts that already exist in your VSA X dashboard — Neo never submits ad-hoc source. To let Neo run on-prem PowerShell (AD / Exchange) through VSA X, register the Neo wrapper script — see [On-prem AD & Exchange setup](/integrations/m365/on-prem#2-upload-the-neo-script-to-your-rmm).
    </Info>
  </Accordion>

  <Accordion title="Patch, Protection, Notifications, System">
    * **Patch management** — read patch policies and global rules
    * **Endpoint protection** — read antivirus policies
    * **Notifications** — read notifications; create notifications and manage webhooks (with write access)
    * **System** — read audit logs, environment info, RBAC scopes, custom field definitions
  </Accordion>
</AccordionGroup>

<Tip>
  Write access is opt-in per area. In Agent Settings → Permission Groups, set the relevant VSA X groups to **Read & Write** to enable creates, updates, and deletes.
</Tip>

## Available Actions

| Category                           | Actions                                                                                                         | Status                 |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------- | ---------------------- |
| **Devices**                        | List/read devices, custom fields, applied policies, antivirus, notifications; move device; update custom fields | Available (read/write) |
| **Assets**                         | Read hardware + installed-software inventory (60 req/hr)                                                        | Available (read)       |
| **Organizations / Sites / Groups** | Read and manage the tenant hierarchy                                                                            | Available (read/write) |
| **Automation**                     | Browse scripts, tasks, workflows and execution history                                                          | Available (read)       |
| **Automation**                     | Execute pre-registered scripts on devices and read results                                                      | Available (read/write) |
| **Patch Management**               | Read patch policies and global rules                                                                            | Available (read)       |
| **Endpoint Protection**            | Read antivirus policies                                                                                         | Available (read)       |
| **Notifications**                  | Read notifications; create notifications and manage webhooks                                                    | Available (read/write) |
| **System**                         | Read audit logs, environment, scopes, custom field definitions                                                  | Available (read)       |

<Info>
  Neo Agent uses the VSA X REST API v3. Make sure your Third-Party Token has the necessary permissions for the areas you want Neo to act in — see the [API token guide](/integrations/rmm/vsax/creating-api-key).
</Info>