In a ChatGPT Business, Enterprise or Edu workspace, an admin can create the ZoomSphere plugin once and publish it to everyone. Members then connect it with their own ZoomSphere login. This article has two parts: what the admin does, and what each member does afterwards.
How this article was written. Our personal ChatGPT guide is photographed from a live account. We do not run a ChatGPT Business workspace, so this part follows OpenAI's own help article "Developer mode and MCP apps in ChatGPT" as of September 2026, and names the settings the way that article does. If a label on your screen differs, the article is the reference and we would like to hear about it.
Part 1: For admins and owners
Step 1: Decide who may use developer mode
Business | Only admins and owners can turn developer mode on and publish a plugin. Members cannot create their own. |
Enterprise and Edu | Admins turn developer mode on for themselves under Settings, Apps, Advanced settings, and can allow it for chosen members through Workspace settings, Permissions & Roles, Connected data using role-based access. |
For a team, the sensible answer is to keep developer mode to admins and publish one shared plugin.
Step 2: Create the plugin at workspace level
In Workspace settings, Apps (Business) or Settings, Apps (Enterprise), choose Create. The form is the same as in the personal guide, Step 3: name ZoomSphere, server address https://mcp.zoomsphere.com/mcp, authentication OAuth. Click Scan tools if the form offers it, then Create. Sign in to ZoomSphere and allow access when asked.
Step 3: Publish it and make it visible
Publish the plugin to the workspace.
Turn on Show in directory, so members can find it under the workspace's own tab in the plugin directory.
On Enterprise and Edu, use role-based access if only some teams should see it.
Two limits to know before you publish. On Business plans a published plugin cannot be updated afterwards; to change anything you delete it and publish again, and every member reconnects. And when we ship new actions, the workspace copy does not see them until an admin refreshes its action list.
Step 4: Tell your team
Publishing makes the plugin visible, it does not sign anyone in. Each member connects with their own ZoomSphere login (Part 2). Send them something like this:
ZoomSphere is now available in ChatGPT. Open chatgpt.com, click Plugins in the left sidebar and look for the workspace tab in the directory. Find ZoomSphere and click Connect, then sign in with your normal ZoomSphere account. Before you use it, open the plugin's page, click Permissions and choose Allow read actions, otherwise ChatGPT may change things in the calendar without asking. In a chat, click the Plugins chip under the message box and pick ZoomSphere.
Known issue, September 2026. Several Business customers report that a published plugin does not show up in members' directories at all. OpenAI has acknowledged it. If your members cannot find ZoomSphere, share the plugin's direct link with them, or open a ticket with OpenAI support and quote this issue.
Part 2: For members
For members whose admin has done Part 1. If you cannot find ZoomSphere anywhere, nobody has published it yet: ask your admin.
Step 1: Find ZoomSphere in the directory
Click Plugins in the left sidebar. Look for your workspace's own tab next to Public, the same place where the Personal tab sits on a personal account. ZoomSphere is listed there with a Connect button. You never see the New Plugin form, your admin has filled it in.
On a personal account the second tab is called Personal. In a workspace it carries your workspace's name.
Step 2: Connect and allow access
Click Connect, then Sign in with ZoomSphere, then Allow Access on the ZoomSphere page. Screenshots are in the personal guide, Step 4.
"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: Set your permission level and use it
Open the plugin's page, click Permissions and choose Allow read actions (personal guide, Step 6). Then attach ZoomSphere in a chat with the Plugins chip (personal guide, Step 7).
What is different for a member | Detail |
No address to type | The admin filled it in. You never see the New Plugin form. |
No developer mode needed | A published plugin does not require the developer mode switch. |
Cannot edit or delete it | You can Disconnect yourself. Changing or removing the plugin is the admin's job. |
Your own ZoomSphere login | ChatGPT acts as you, with exactly the workspaces and channels your ZoomSphere account has. |
Something not working? See ZoomSphere MCP: troubleshooting and security.