> ## 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 Professional Services Automation system — Neo reads tickets, writes updates, and orchestrates workflows through it

<Warning>Connecting your PSA first is mandatory. Neo reads incoming tickets, writes notes and time entries, drives state transitions, and triggers workflows entirely through your PSA.</Warning>

Neo speaks every supported PSA's API natively and treats them uniformly — the same workflows, agents, actions, and triggers work across all four. Pick yours below to begin setup.

## Supported PSA Platforms

<CardGroup cols={2}>
  <Card title="Autotask" icon="ticket" href="/integrations/psa/autotask/overview">
    Connect via API user + security level. Three-step setup with end-user notification controls.
  </Card>

  <Card title="ConnectWise" icon="briefcase" href="/integrations/psa/connectwise/overview">
    Connect via dedicated security role + API member. Optional Pod integration to embed Neo inside ConnectWise.
  </Card>

  <Card title="HaloPSA" icon="circle-half-stroke" href="/integrations/psa/halopsa/overview">
    Connect via Agent Resource + OAuth API application with scoped permissions.
  </Card>

  <Card title="ServiceNow" icon="gear" href="/integrations/psa/servicenow/overview">
    Connect via OAuth 2.0 — Neo provisions Business Rule + System Property webhooks automatically. Supports the full task family (incidents, requests, RITMs, catalog tasks, change requests, problems).
  </Card>
</CardGroup>

## What Neo Does With Your PSA

Neo reads incoming tickets in real time, then writes back the results of agent work:

* **Read** — tickets and time entries (with all custom fields), companies, contacts, configurations, statuses, queues, ticket types
* **Triage** — status, priority, queue, type/subtype, owner, custom fields
* **Communicate** — internal notes, customer-facing notes, email replies routed through the PSA
* **Time tracking** — time entries attributed to a dedicated Neo agent resource
* **Lifecycle** — create new tickets, merge duplicates, schedule entries, state transitions
* **Webhooks** — real-time callbacks on ticket events so workflows fire the moment they need to

## How Permissions Work

Neo uses **two layers of access control**:

1. The PSA-side permissions on the API user, security role, or OAuth app set the *maximum* possible access (configured during setup).
2. The Neo dashboard's per-agent permission groups control what each agent actually does — read-only vs read/write, with optional technician approval for destructive operations.

A junior helpdesk agent can be allowed to add notes but not change priority, while a senior dispatch agent can do both — all from the same PSA connection.

## Prerequisites

Before connecting any PSA you'll need:

* Administrative access to create an API user, security role, or OAuth application (varies by PSA — see the per-platform guide above)
* A dedicated agent resource or service account that Neo's writes will be attributed to (improves your audit trail)
* The Neo Agent dashboard at [dashboard.neoagent.io](https://dashboard.neoagent.io/integrations)

Select your PSA above for the step-by-step setup guide.