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

> Save a Wizer API key in Neo, and decide what each agent can do

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

## 1. Copy your API key

<Steps>
  <Step title="Sign in to your partner account">
    Sign in to the Wizer admin panel with your partner account, so the key reaches every client company.
  </Step>

  <Step title="Copy the key">
    Open **Settings**, then **Integration**, and copy the API key. Generate one if none exists.
  </Step>
</Steps>

## 2. Add the key in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open **Integrations** and find the Wizer card, under Security.
  </Step>

  <Step title="Save the key">
    Paste the key and click **Save**. Neo checks it against Wizer's Partner Portal before saving, so a wrong key, or one that is not your partner account's, is rejected straight away. The **Organization Mapping** tab fills separately after the save, and again on each nightly PSA sync.
  </Step>
</Steps>

## 3. Turn Wizer on per agent

Open the agent, go to the Integrations section, and configure the Wizer block.

### Pick an access profile

<CardGroup cols={2}>
  <Card title="Read Only" icon="magnifying-glass">
    Read users, client companies and training progress. Nothing is changed.
  </Card>

  <Card title="Helpdesk" icon="headset">
    Add, disable and regroup users, and start or share training, with technician approval.
  </Card>

  <Card title="IT Admin" icon="user-gear">
    Add, disable and regroup users, and start or share training, on its own.
  </Card>

  <Card title="Full Automation" icon="bolt">
    Manage users and training assignments without approval.
  </Card>
</CardGroup>

### Or set each area by hand

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Users** | Disabled, Read Only, Read and Write | Users, groups and departments of a client. Write adds, disables, renames and regroups users. |
| **Training Assignments** | Disabled, Read Only, Read and Write | Start or share a course for a client. Read checks a batch operation. |
| **Reports** | Disabled, Read Only | Training, policy, video and phishing progress. |
| **Customers** | Disabled, Read Only | The client companies under your partner account. |

## Safety controls

* **You decide what waits on a technician.** Each area has its own approval setting. Helpdesk asks on every user change and every course start; IT Admin and Full Automation ask on nothing.
* **Leavers are disabled, never deleted.** Disabling keeps the user's training record, which your clients may need as compliance evidence. Neo does not delete Wizer users.
* **A batch names its clients.** Neo refuses a course start or share for "all customers" at once. The agent names each client company.
* **Only what the job needs.** Neo sends only user, training, report and customer-list requests. Login links, inviting or disabling a client company, and launching phishing campaigns are unreachable.
* **Path safety.** A URL path with a `..` segment is rejected before it reaches Wizer.

## If Wizer refuses Neo's requests

| What comes back | Cause | Fix |
| - | - | - |
| `401` | The key was regenerated or removed, or it is not your partner account's key | Copy the current key from your Wizer partner account and save it in Neo |
| `403` | The key may not use that area, for example a direct (non-partner) account on a partner endpoint | Use your partner account's key, or ask Wizer support to enable the endpoint |
| `429` | Rate limited | Wait. Neo retries a read a few times first; if the limit holds, the agent stops calling Wizer for that run and reports the call it could not make |
| A failed **Wizer Company Mapping** row with a `401` or `403` | The key is refused, or it is not a partner key | Fix the key as above. The next PSA sync rebuilds the mapping |

## Disconnecting Wizer

In the Neo Dashboard, open **Integrations**, select the Wizer card, click **Disconnect** and confirm. Neo removes the key from Key Vault. Agents that use Wizer stop working until you connect it again. Your Organization Mapping is kept, including any mapping you set by hand.

## Security

* The key lives in Azure Key Vault. It is never stored in plaintext.
* All traffic goes over HTTPS to `gateway.wizer-training.com`.
* Write access is opt in per agent and per area.


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