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

> Create a CloudRadial API key and save it in Neo

You connect CloudRadial once at the MSP level. One API key covers every client company in your portal.

## 1. Create the API key

**1. Check that the API is on**

Sign in to CloudRadial as an admin. Under **Configuration > Integrations**, check that **API** is enabled.

**2. Add a key**

Open **Partner > Settings > Integrations > API** and click **Add API Key**. Name it Neo.

**3. Copy both keys**

Copy the **public key** and the **private key**. The private key shows only once.

**4. Note your region**

Your CloudRadial portal runs in the **US** or the **EU** region. When you are not sure, ask CloudRadial support which API address your portal uses: `api.us.cloudradial.com` or `api.eu.cloudradial.com`.

> [!WARNING]
>
> When you delete the key in CloudRadial, Neo loses access until you save a new key here.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the CloudRadial card, under Customer Success.

**2. Save the key**

Pick the region, paste the public and private keys and click **Save settings**. Neo checks the key against CloudRadial before saving, so a wrong key, or a key for the other region, is rejected straight away.

**3. Check the mapping**

Open the card's **Organization Mapping** tab and confirm each client's CloudRadial company, or set it by hand. On a ticket, Neo works only with the company mapped to the ticket's company.

## 3. Turn CloudRadial on per agent

Open the agent, go to its **Tools & Settings** tab, click **Customer Success**, and expand the **CloudRadial** block. Pick a preset, or set each area yourself:

| Preset | What runs |
| - | - |
| **Read Only** | Reads forms, users, companies, endpoints, content, courses and messages |
| **Helpdesk** | Reads everything; a technician approves each change to a form, user, endpoint or content. Companies and Signal messages stay read-only |
| **IT Admin** | Builds forms and manages users, endpoints, content and courses on its own; a technician approves each Signal message |
| **Full Automation** | Everything, without approval |

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Service Catalog** | Disabled, Read Only, Read / Write | Request forms, their questions, categories, approval settings and PSA routing. |
| **Portal Users** | Disabled, Read Only, Read / Write | Each client's portal users. |
| **Companies & Domains** | Disabled, Read Only, Read / Write | Companies and company groups, domains, certificates and replacement tokens. Deleting a company always asks a technician. |
| **Endpoints** | Disabled, Read Only, Read / Write | Endpoints, installed software, custom properties and Windows services. |
| **Portal Content** | Disabled, Read Only, Read / Write | Articles, menus, quickstarts, Planner products, media and report archives. |
| **Feedback & Assessments** | Disabled, Read Only, Read / Write | End-user feedback and assessments. |
| **Training** | Disabled, Read Only, Read / Write | Courses, lessons and enrolments. |
| **Flexible Assets** | Disabled, Read Only, Read / Write | Flexible asset types, fields and records. |
| **Signal Messages** | Disabled, Read Only, Read / Write | Messages to client users' devices, and the enrolled devices. |

## A form-design agent

To have Neo design forms in a chat, give a chat agent **Service Catalog** at Read / Write and **Companies & Domains** at Read Only, so it can find the client's CloudRadial company, and **Agents & Schemas** at Read Only under Neo API, so it can read what your other agents need from a ticket. Then ask it, for example: "Create a user-friendly Leavers form for Acme that asks for everything our Leaver agent needs, and send it for approval to the client's manager."

See [CloudRadial API](https://docs.neoagent.io/agents/tools/sales/cloudradial-api.md) for what the agent can do.


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