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

> Copy your usecure API key and save it in Neo

You connect usecure once at the MSP level. The API key of your MSP account covers every client company under it. A single client's own usecure account can be connected with that account's key instead.

## 1. Copy the API key

**1. Turn on API access**

usecure turns API access on by request. If your console has no API page under **Settings**, ask usecure support to enable the API for your account.

**2. Copy the key**

Sign in to the usecure console ([eu.usecure.io](https://eu.usecure.io), or [us.usecure.io](https://us.usecure.io) in the United States) and open **Settings > API**. Copy the **API Key**. The **Client API Key** on the same page is for prospect sign-up pages, and Neo does not use it.

> [!WARNING]
>
> Do not regenerate the key in usecure after you connect it. Neo loses access until you save the new key here.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the usecure card, under Security.

**2. Save the key**

Choose the region your console is on, paste the API key and click **Save settings**. Neo checks it against usecure before saving, so a wrong key or region is rejected straight away.

## 3. Turn usecure on per agent

Open the agent, go to its **Tools & Settings** tab, click **Security**, and expand the **usecure** block. Pick one of its **Presets**, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Customer Accounts** | Disabled, Read Only, Read / Write | Your client companies, their plan, settings and usage; creating, updating, suspending, deleting and restoring a client or a prospect. Deleting a client always asks a technician. |
| **Learners & Groups** | Disabled, Read Only, Read / Write | The users who take training, their groups and group managers. |
| **Admin Users** | Disabled, Read Only, Read / Write | Who signs in to the usecure console for a client. |
| **Training** | Disabled, Read Only, Read / Write | The course library, enrolments, results, gap analysis and reports. |
| **Phishing Simulations** | Disabled, Read Only | Simulations and each recipient's results. |
| **Policies** | Disabled, Read Only, Read / Write | Policies, policy templates and signatures; sending a policy to sign. |
| **Breaches & Risk** | Disabled, Read Only | Breached accounts and services, and each client's risk score. |

To check a reported email, an agent needs Read Only on Learners & Groups, Training, Phishing Simulations and Policies.

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read, and enrolling learners on training | Learner and policy changes. Admin user and client account changes are off |
| **IT Admin** | Every read, learners, training and policies | Admin user and client account changes |
| **Full Automation** | Every read and write | Deleting a client account |

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


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