Connecting an AI assistant: what it reads, how, and what it never does.

Before you connect

An owner or admin switches AI assistants on at Settings › AI assistants. The switch sits behind an acknowledgement: that members may connect assistants whose providers receive what those members ask for, under the member's own account with that provider, with WAOversight not party to it. Until it is on, an assistant that connects is refused and told why.

The workspace needs a live subscription or its trial, on any plan. You need a WAOversight login: owners, admins, managers and auditors can connect; reps have no login and cannot. Each person connects their own assistant and signs in as themselves.

Every assistant takes the same address and then sends you to WAOversight to sign in and allow it. The sign-in page says which assistant is asking, where its code goes, which login it will read as and what it may read, and asks you to accept that what you ask for goes to that assistant's provider under your own terms with them. An app whose code goes somewhere other than a known assistant is shown as unverified.

The address, for every client:

https://mcp.waoversight.com/mcp

Claude, on the web, desktop, mobile and in Cowork

1. Open Customize › Connectors.
2. Choose Add custom connector and paste the address.
3. Sign in with your WAOversight login when Claude asks, and press Allow.

Once WAOversight is in the Claude directory, you will find it there instead of adding it by hand. On a Team or Enterprise plan an owner adds it for the organisation, and each member still connects with their own login. Claude asks to stay connected, so you are not asked to sign in again for up to 90 days.

Claude Code

Run this in a terminal, then /mcp to sign in:

claude mcp add --transport http waoversight https://mcp.waoversight.com/mcp

ChatGPT

1. Open Settings › Connectors › Advanced and switch on Developer mode.
2. Choose Create and paste the address.
3. Sign in with your WAOversight login when ChatGPT asks, and press Allow.

On a Business or Enterprise workspace an admin creates the connector. Once the plugin is listed in ChatGPT's directory, you will find it there.

Cursor and VS Code

Add the server to your mcp.json and sign in when the editor asks:

{
  "mcpServers": {
    "waoversight": { "url": "https://mcp.waoversight.com/mcp" }
  }
}

Microsoft 365 Copilot and Gemini Enterprise

Both connect through their admin centres rather than from a settings page of your own: ask your administrator to add the server address there, as a custom MCP connector in Copilot or a custom MCP server in Gemini Enterprise. The sign-in and everything after it are the same: one WAOversight login, reading only what that login can see.

What the assistant may read

What your login can read, and nothing else. A manager's assistant sees that manager's teams, an auditor's reads, an owner's sees the workspace. A team you do not manage is not visible to it, and the reply says nothing about that team's existence.

Replies are paged: 50 messages or 25 list rows at a time, up to 100, and never more than 100 KB in one reply. A larger export comes back as a sign-in link to the dashboard's download instead. Files come back as a list with a sign-in link, never the file itself. Nothing is redacted: you asked for the customer by name, and the reply is your own read.

The caps

Each connection may make 60 calls a minute and 1,000 an hour. The workspace as a whole may make 600 a minute and 10,000 an hour, and has a daily cap an owner or admin sets at Settings › AI assistants: 5,000 calls by default, anywhere from 100 to 1,000,000, counted on the workspace's clock. Past any of these the assistant is told to wait, and how long. A refused call is counted, and writes nothing to the access audit.

Ending a connection

Your own: under Your account, where each is listed with Revoke. Anyone's: an owner or admin, at Settings › AI assistants, where every connection is listed with who, which assistant, what it may read, when it was made and when it last read. Switching AI assistants off ends every connection at once, and switching on again starts from none.

A revoked connection ends on the assistant's next request. So does one whose login was disabled, whose password changed, or whose role or teams changed: every call checks again. An ended connection stays listed, so the record of which assistant could read as whom is kept.

The audit

Every read an assistant makes is written to the access audit before any data is returned, the same row your dashboard would write for the same read, with the assistant named beside you. If the row cannot be written, the assistant gets an error and no content. The Access audit page filters by AI assistant, so "read by Claude for Megan Foster" is a row you can find.

Connecting an assistant emails you: which assistant, when, from where, and what it may read. If it was not you, revoke it from Your account and reset your password.

When it does not connect

Privacy

What you ask the assistant for, which can include message content, names and phone numbers, is sent to that assistant's provider under your own account's terms with them. WAOversight is not party to that agreement, does not redact what is sent, and stores nothing of what was asked or answered: the settings page shows counts, the access audit shows the reads. The full statement is in the privacy policy and the data processing agreement, and the case for the feature is on AI assistants.