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

​
1. Copy your API key

1

Sign in to your partner account

Sign in to the Wizer admin panel with your partner account, so the key reaches every client company.
2

Copy the key

Open Settings, then Integration, and copy the API key. Generate one if none exists.

​
2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Wizer card, under Security.
2

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.

​
3. Turn Wizer on per agent

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

​
Pick an access profile

Read Only

Read users, client companies and training progress. Nothing is changed.

Helpdesk

Add, disable and regroup users, and start or share training, with technician approval.

IT Admin

Add, disable and regroup users, and start or share training, on its own.

Full Automation

Manage users and training assignments without approval.

​
Or set each area by hand

​
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

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