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

> Create a WOSP API key, save it in Neo with your WOSP address, and turn WOSP on per agent

You connect WOSP once at the MSP level. One API key with tenant scope **All** reaches every customer tenant in your WOSP.

## Before you start

Neo calls your WOSP over the internet. Your WOSP must answer at a public HTTPS address with a certificate from a public authority, as it does when your technicians open it from home. If you allow only some addresses, add Neo's addresses ([IP whitelisting](https://docs.neoagent.io/integrations/ip-whitelisting.md)).

## 1. Create an API key

**1. Open API keys**

Sign in to WOSP as a platform admin and open **Settings**, then **API keys**.

**2. Create the key**

Create a key with a description such as "Neo", tenant scope **All**, and **Write enabled** turned on so Neo can make changes. A key without Write enabled only reads. Set an expiry that suits your policy, and note it: Neo stops when the key expires.

**3. Copy it**

Copy the key when WOSP shows it. It starts with `wosp_`. An MCP token (`wospmcp_`) does not work here.

## 2. Add the key in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the WOSP card, under Identity & Workspace.

**2. Save the address and the key**

Enter the **WOSP Address**, the address you open WOSP at (for example `https://wosp.example.com`), paste the **API Key**, and click **Save**. Neo lists your tenants with the key before saving, so a wrong address or key is reported straight away.

Neo then maps your tenants to your PSA companies on the **Organization Mapping** tab. To make the mapping exact, set each tenant's alias in WOSP to the customer's name in your PSA.

## 3. Turn WOSP on per agent

Open the agent, go to the **Tools & Settings** tab, and configure the WOSP block under **Tools & Integrations**. Pick a profile, or set each area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Users** | Disabled, Read Only, Read/Write | Suspend, restore, sign out, reset passwords, aliases. Helpdesk asks a technician before a change. |
| **Groups** | Disabled, Read Only, Read/Write | Groups, members and group settings. Helpdesk asks before a change. |
| **Gmail Settings and Delegation** | Disabled, Read Only, Read/Write | Out of office, forwarding, delegates, send-as. Helpdesk and IT Admin ask before a change. |
| **Licenses** | Disabled, Read Only, Read/Write | Helpdesk asks before a change. |
| **Devices and Browsers** | Disabled, Read Only, Read/Write | Wiping, powerwashing or deprovisioning a device always asks. |
| **Shared Drives and Drive Transfer** | Disabled, Read Only, Read/Write | Shared drives and moving a user's Drive files. |
| **Org Units, Domains and Calendar Resources** | Disabled, Read Only, Read/Write | Editing a building or a calendar resource always asks. |
| **Admin Roles** | Disabled, Read Only, Read/Write | IT Admin asks a technician before a change. |
| **Alerts, Audit Findings and Third-Party Apps** | Disabled, Read Only, Read/Write | Revoking an app's access and deleting alerts. |
| **Reports and Activity** | Disabled, Read Only | Audit reports and activity. |
| **Chat Spaces and Classroom** | Disabled, Read Only, Read/Write | Deleting spaces and removing members. |
| **Tenants and Data Collection** | Disabled, Read Only, Read/Write | Renaming or updating a tenant, deleting it, or hiding it from the API always asks. |
| **WOSP Settings and Onboarding** | Disabled, Read Only, Read/Write | Neo reads WOSP's settings and never changes them. Changing WOSP's sign-in always asks. IT Admin asks before any change. |

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

## Set up an agent

Ask your Neo Support Agent for the agent you need, for example: "Set up a triggered agent for offboarding tickets of my Google Workspace customers. Through WOSP it signs the leaver out, suspends them, gives their manager access to their mailbox, moves their Drive files to the manager, and notes each step on the ticket."


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