> ## 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 HaloPSA system to Neo Agent for automated ticket management and workflow automation

## Setup Overview

Setting up the HaloPSA integration involves three main steps:

<CardGroup cols={2}>
  <Card title="Creating an Agent Resource" icon="user-plus" href="/integrations/psa/halopsa/creating-agent">
    Set up a dedicated agent in HaloPSA that Neo Agent will use for time entries, ticket assignments, and action attribution.
  </Card>

  <Card title="Creating an API Application" icon="key" href="/integrations/psa/halopsa/creating-api-application">
    Configure API credentials with the right scopes for Neo Agent to access your HaloPSA system programmatically.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Connecting to Neo Agent" icon="link" href="/integrations/psa/halopsa/connecting-to-neo">
    Configure the connection between your HaloPSA system and Neo Agent using API credentials and integration settings.
  </Card>

  <Card title="Configuring Webhook Events" icon="webhook" href="/integrations/psa/halopsa/configuring-webhooks">
    Configure which ticket events trigger real-time notifications to Neo Agent.
  </Card>
</CardGroup>

## How Permissions Work

Neo Agent uses **two layers of access control**: the HaloPSA API application's OAuth scopes set the *maximum* API access (configured during setup), while the Neo Agent dashboard controls what Neo actually does — which areas it can read, write, or ignore, and whether actions require technician approval.

## Prerequisites

Before starting the integration setup, ensure you have:

* **Admin Access**: Administrative access to your HaloPSA system (Configuration section)
* **API Access**: An active HaloPSA subscription with API access enabled
* **Named Licence**: An available agent licence for the Neo Agent resource