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

# Connecting Axcient to Neo

> Create an Axcient API key in the x360Portal and save it in Neo

You connect Axcient once at the MSP level. One API key covers every client and reads x360Recover, x360Cloud, x360Sync and billing.

## 1. Create the API key

<Steps>
  <Step title="Open API Keys">
    Sign in to the Axcient x360Portal at [partner.axcient.com](https://partner.axcient.com) as an administrator and open **Settings > API Keys**.
  </Step>

  <Step title="Add the key">
    Choose **Add API Key**, name it Neo, and choose **Generate API Key**.
  </Step>

  <Step title="Copy the key">
    Copy the key.
  </Step>
</Steps>

<Warning>
  Every administrator in your x360Portal can see and delete API keys. If someone deletes the Neo key, Neo loses access until you save a new key here.
</Warning>

## 2. Add the key in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open **Integrations** and find the Axcient card, under Backup & Recovery.
  </Step>

  <Step title="Save the key">
    Paste the API key and click **Save settings**. Neo checks it against Axcient before saving, so a wrong key is rejected straight away.
  </Step>
</Steps>

## 3. Turn Axcient on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Axcient block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **x360Recover Backups** | Disabled, Read Only | Clients, protected devices, backup jobs and their runs, AutoVerify tests, restore points, appliances, vaults and storage use. |
| **Vault Connectivity Thresholds** | Disabled, Read Only, Read / Write | How many minutes a vault may lose its connection before Axcient marks it warned. A higher threshold delays the warning. |
| **Organization and Portal Users** | Disabled, Read Only | Your partner organization and the x360Portal users who sign in to it. |
| **x360Cloud Backups** | Disabled, Read Only | Microsoft 365 and Google Workspace backup status, users and shared sites. |
| **x360Sync Files** | Disabled, Read Only | Users, groups, guests, machines, folders, activity and usage. |
| **x360Sync Share Links** | Disabled, Read Only | Who shared what, with whom, and how often it was opened. Neo hides each link's address. |
| **Billing Usage** | Disabled, Read Only | Your actual and billable usage by month. |

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read except billing | A vault threshold change |
| **IT Admin** | Every read | A vault threshold change |
| **Full Automation** | Every read and write | Nothing |

## Use it on backup alert tickets

Axcient's alert emails name the protected system, the client and the appliance, for example `Failed Backup on SRV-001 at AcmeLaw on ACME-BDR-001`. An agent that triggers on those tickets can confirm a successful run, quote the error of a failed one, and check the last AutoVerify. Map each client on the Organization Mapping tab first: on a ticket, the agent reads only the client mapped to the ticket's company.

Axcient can send a ticket for every successful backup. If yours does, filter the agent's trigger to failed and missed backups, and let a scheduled agent report the successful ones once a day.

See [Axcient API](/agents/tools/backup/axcient-api) for what the agent can read and change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.