> ## 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 Redstor to Neo

> Create a RedAPI service account, save it in Neo and turn it on for the agents that handle backup failures

You connect Redstor once at the MSP level, then turn it on per agent.

<Note>
  Redstor offers the RedAPI to partners on its new pricing plan, and only a **Partner Admin** can create a service account. If you do not see the RedAPI icon in the RedApp, ask your Redstor account manager to turn it on.
</Note>

## 1. Create a RedAPI service account

<Steps>
  <Step title="Open Service accounts">
    Sign in to the RedApp as a Partner Admin, click the **RedAPI** icon at the top right, and open **Service accounts**.
  </Step>

  <Step title="Add the account">
    Click **Add a service account**, name it "Neo", and under **Partner and company access** assign your partner with the clients Neo should reach. Turn on **Auto-assign all future customers** so new clients are included.
  </Step>

  <Step title="Create a key">
    Under **Keys**, click **Create key**, name it, and confirm with your RedApp sign-in. Click **Download** to save the key files. The private key is offered only once.
  </Step>

  <Step title="Copy the Client ID">
    Click **Add account**. The new account shows on the Service accounts page with its **Client ID**.
  </Step>
</Steps>

## 2. Add the service account in Neo

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

  <Step title="Save the account">
    Paste the **Client ID**, then open the private key file you downloaded and paste its whole content (the JSON that starts with `{"kty": "RSA"`) into **Private key**. Click **Save**. Neo signs in to Redstor with them before saving, so a wrong or revoked key is rejected straight away. The **Organization Mapping** tab fills separately after the save, and again on each nightly PSA sync.
  </Step>
</Steps>

## 3. Turn Redstor on per agent

Open the agent, go to the Integrations section, and configure the Redstor block. Pick a profile, then change any area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Backup & Restore Status** | Disabled, Read Only | Backup and restore results per account, backup errors, backup accounts and storage regions. This is the area a backup-failure agent needs. |
| **Customers** | Disabled, Read Only, Read / Write | Your RedApp clients. Deleting, disabling or moving one to another partner, and adding a sub-partner, always ask a technician. |
| **Products & Subscriptions** | Disabled, Read Only, Read / Write | The product catalogue and each client's subscriptions. Adding a paid product and converting a trial bill you; removing a product always asks a technician. |
| **Consumption** | Disabled, Read Only | Data protected, seats and workloads. |
| **RedApp Users** | Disabled, Read Only | Who can sign in to the RedApp, and the status and expiry of a RedAPI service account's keys. |

The **Read Only** profile reads every area. **Helpdesk** also changes clients and subscriptions, each with a technician's approval. **IT Admin** adds and enables clients on its own and asks before subscription changes. **Full Automation** asks only for the changes that always ask.

## Example: close backup error reports that have recovered

Give an agent that runs on your Redstor error report tickets (from `noreply@redstor.com`) the Redstor **Read Only** profile and your PSA's ticket permissions, and instructions like these:

> For a Redstor backup error report, check each backup account it covers in Redstor. If every account that failed has a successful backup after its last failure, and every account that missed a backup has one after the report, add an internal note with the accounts and their backup times and close the ticket. Otherwise leave the ticket open and note each account that is still failing with its latest error.

A scheduled agent that runs a few times a day works well for this, because the next successful backup can come hours after the report. See [Redstor API](/agents/tools/backup/redstor-api) for what the agent can read and change.


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