Skip to main content

Claude for Teams: Rolling Out ZoomSphere to Your Organization

For Claude Team and Enterprise: how an Owner adds ZoomSphere once for everyone, and what each member does to connect.

Written by Jakub Mach

On Claude Team and Enterprise plans, an Owner can add ZoomSphere once for the whole organization. Every member then finds it in their connector list, pre-filled and pre-approved, and connects it with their own ZoomSphere login. This article has two parts: what the Owner does, and what each member does afterwards.

The one thing teams get wrong. Adding ZoomSphere at organization level does not connect anyone. It only makes the connector appear in every member's list. Each person still signs in to ZoomSphere themselves. That is deliberate: everybody acts under their own ZoomSphere permissions, and you can see who did what.

You do not have to do this, any member can add ZoomSphere for themselves with the personal guide. You do it because it gives you one correct address instead of fifteen people copying a URL, a connector that is already there when a new colleague joins, and per-tool limits for the whole organization.

Part 1: For Owners

Only Owners and Primary Owners can do this. Admin settings exist only in the browser.

Step 1: Open admin settings

  1. Click your name in the bottom-left corner.

  2. Click Organization settings. Only Owners see this item.

  3. In the admin sidebar, scroll down to the group Libraries & Access and click Connectors.

The account menu. Markers 1, 2: your name, then Organization settings.

The admin sidebar, scrolled down. Marker 3: Connectors, between Plugins and Skills.

Step 2: Add, then Custom, then Web

  1. Click Add in the top-right corner, then Custom.

  2. Choose Web. The ZoomSphere MCP server is a hosted HTTPS service, not something installed on each machine.

The organization's connector list with the Add menu open.

Custom, then Web.

Step 3: Name and address

The dialog is the same as in the personal guide: name ZoomSphere, URL https://mcp.zoomsphere.com/mcp, then Continue. Copy the address, do not retype it: it cannot be edited afterwards.

Exactly how it should look before you click Continue.

Step 4: Check the connector details

ZoomSphere is now in the organization list. Type says Web with a Custom badge and Authorization says Individual, which means every member signs in as themselves. The list is alphabetical, so ZoomSphere is usually on the last page.

ZoomSphere in the organization connector list.

Click the three dots at the right end of the row and choose See details. The same menu holds Refresh tools list, which you will need when we ship new tools, and Delete, which removes the connector for the whole organization.

Three dots: See details, Refresh tools list, Delete.

The admin detail view.

OAuth client ID and secret

Leave both empty. They are for servers that require you to register your own OAuth application. ZoomSphere does not.

Browser sign-in

Leave it on. This is what lets each member sign in to ZoomSphere as themselves. Turn it off and nobody can connect.

Managed authorization

Optional, and only if your organization uses a supported identity provider for SSO. If you are not sure, skip it. Browser sign-in works for everyone.

Step 5: Set the organization-wide limits

Scroll down in the same panel to Tool permission restrictions. What you set here is a ceiling: a member can always choose something stricter for themselves, never looser.

Tool permission restrictions. Read the two middle paragraphs, they say where these limits apply and where they do not.

Default restriction for unconfigured tools

Set this one first. It covers every tool you do not configure by hand, including tools the connector gains later. Leave it on Always allow and a tool we ship next month is allowed the day it appears.

Per-tool rows

Grouped into read-only and write or delete, exactly like the personal view.

Per-tool rows. Each also states what members are still free to choose.

These limits do not cover everything. They apply to Claude.ai, the Claude desktop app and Claude Code on the web. They do not apply to the Claude Code CLI, to desktop extensions, or to the Claude API, even when those connect to the same ZoomSphere connector.

A sensible starting point for agencies: allow everything that reads or drafts, keep a human in the loop for anything that goes live, then let each person tune their own permissions.

Step 6: Tell your team

ZoomSphere now appears in every member's connector list as not connected. Send them Part 2 of this article, or something like this:

ZoomSphere is now available in Claude. Open Claude, click your name at the bottom-left, then Settings. In the sidebar find the Customize group and click Connectors. Stay on Your connectors with the filter on All. Find ZoomSphere and click Connect, then sign in with your normal ZoomSphere account. Nothing to type, the address is already filled in. On the authorization screen you will see a note that the application is not verified; that is expected during early access, the connector is ours. Then, in any chat, click +, then Connectors, and switch ZoomSphere on.

Worth knowing: you cannot prevent members from adding their own personal custom connectors. If you want everyone on the same configuration, provide it centrally and say so.

Part 2: For members

For Team and Enterprise members whose Owner has done Part 1. If ZoomSphere is not in your list at all, nobody has added it yet: use the personal guide instead.

Step 1: Find ZoomSphere in your list

Open the connectors screen (Settings, Customize, Connectors in a browser, or Customize, Connectors, Yours in the desktop app). Stay on Your connectors with the filter on All. The ZoomSphere row is already there: Web with a Custom badge, an empty Authorization column, and a Connect button instead of a check mark.

  1. Click Connect on the ZoomSphere row.

ZoomSphere as a member sees it before connecting. Marker 1: Connect.

If you opened the row instead: the same choice inside. Marker 2: Connect.

Step 2: Sign in to ZoomSphere and allow access

Claude takes you to app.zoomsphere.com. Log in if needed, check the redirect address, the permissions and the account, then click Allow Access.

The ZoomSphere authorization screen.

"This application is not verified by ZoomSphere." Expected during early access. It appears for every application that has not been through our formal review yet, our own included. The notice goes away once the integration leaves early access.

Step 3: Check that it says connected

Back in Claude, the same row now says Individual and shows a check mark.

The same row, ten seconds later.

Step 4: Set your permissions and switch it on

Open the ZoomSphere row and set Tool permissions (Steps 5 and 6 of the personal guide). If your Owner set an organization-wide limit for a tool, you can only pick something equal or stricter; the row tells you what you may choose. Then switch ZoomSphere on in a chat with the + menu.

What is different for a member

Detail

No address to type

The Owner filled it in. You never see the Add dialog.

No Organization settings

Your account menu has no Organization settings row. That is normal.

Cannot remove the connector

You can Disconnect yourself. Removing it for everyone is the Owner's job.

Permissions have a ceiling

Your Owner's limits apply. Stricter is always allowed, looser is not.

Did this answer your question?