ChatGPT Enterprise Admin Checklist: What the September 29 Rollout Turned On, and What Waits for You

A ChatGPT Enterprise admin got eight new items on September 29, 2026, and a new Admin console screen on October 1. Most of the new features stay off until an admin acts. A few change what your existing settings reach, and those deserve a look this week.

OpenAI posted the changes in its Enterprise and Edu release notes and its Business release notes. This piece is for the admin at a university, association or agency. It covers what each feature does, which plans get it, its default, and where to control it. Status is as of October 6, 2026.

The short version for a ChatGPT Enterprise admin: GPT-6.1 Sol needs you to turn it on for Enterprise and Edu. Team tasks and @ChatGPT run on workspace connections, which act with the connected account’s permissions, not the user’s. Connected apps in Sites stay off per plugin until you allow them. And the new Plugins and Marketplaces tabs bring a default worth knowing: imported plugin marketplaces sync daily.

What the ChatGPT Enterprise admin release notes list

This table combines the Enterprise and Edu notes, the Business notes and OpenAI’s general ChatGPT release notes.

Dots also arrived on September 29. The general notes say: "Enterprise access is a beta and is off by default." See What Are OpenAI’s Dots? for details.

Edu admins: read the plan lines closely

The Enterprise and Edu notes name Edu in only two of the September 29 items: Sites and GPT-6.1 Sol. Team tasks, team sharing, @ChatGPT and Codex Cloud are each described as available in Enterprise workspaces.

That may be a wording choice, or Edu may get these later. OpenAI does not say. If you run a university workspace, check your own Admin console before you plan a rollout. If a setting is missing, ask your OpenAI account team rather than assume.

The Business notes list most of the same items, without OpenAI Marketplace.

GPT-6.1 Sol is off until you turn it on

GPT-6.1 Sol is OpenAI’s newer, cheaper model for agentic work. It runs in ChatGPT Work and Codex. OpenAI’s announcement says it is "not yet available in Chat."

The two OpenAI sources differ on timing. The announcement says it is available "starting today" to Plus, Pro, Business, Enterprise and Edu users. The release notes say it is rolling out, starting with Pro, and that "Enterprise and Edu administrators must enable access."

The general release notes give the path. Enterprise and Edu owners enable it in Workspace settings > Permissions & roles, on the Workspace tab or through a custom role.

When staff cannot see it, this is the first thing a ChatGPT Enterprise admin should check. Our OpenAI DevDay 2026 recap covers the model and its pricing.

Workspace connections act with someone else’s access

Workspace connections are the piece most likely to surprise a ChatGPT Enterprise admin. An admin connects a company-managed account once, such as a shared Google Drive or project tracker login. Team tasks and @ChatGPT then use that account so each person does not connect their own.

OpenAI’s workspace connections guide is plain about the trade-off: "Actions use the connected account’s permissions, which may exceed your personal access." It also warns: "A workspace connection may read sources you cannot open."

You create one in the Admin console under Workspace connections, then choose who can find, use and manage it.

For an association, that might mean a read-only AMS report user, not the AMS admin login. For a university, keep registrar and financial aid systems out of shared connections unless policy allows it.

Team tasks and teams

Teams let people group coworkers once, then share Pages or whole Spaces with the group. Team tasks are recurring jobs that run on a schedule or a trigger, such as a weekly project digest.

The teams admin guide names two permissions: Create teams, and Create and manage team automations. You set them through workspace settings or custom roles.

Three points from that guide matter for a ChatGPT Enterprise admin:

• Tasks run as the team. They use the team’s service account and its configured connections, not the person who set them up.
• New members see history. The guide says: “New members can see all earlier runs and generated files.” You cannot restrict single runs.
• Membership does not share everything. Joining a team does not share personal chats or connections, and it does not override access controls.

Before you grant Create teams widely, decide who should own a team. Agencies with client teams should keep each client’s work in its own team.

@ChatGPT in Slack and Microsoft Teams

Staff can now DM @ChatGPT or mention it in a channel to summarize a thread, answer a question or draft something. The Business notes say: "Your organization must install and enable @ChatGPT before you can use it."

Setup takes two admins: the ChatGPT admin connects the workspace, and the Slack or Teams admin installs the app. The @ChatGPT admin guide also lets you limit it to selected channels.

The key line in that guide: @ChatGPT "does not inherit a person’s file, app, or private-channel access." It uses the plugins and workspace connections you assign. Replies in shared conversations are visible to everyone in them.

For a ChatGPT Enterprise admin, the risk sits with the assigned connections. Start with one or two channels and a narrow connection list.

Connected apps in Sites stay off per plugin

Sites are small web pages people build in ChatGPT. On September 29, members gained the ability to build private Sites that pull from connected apps. Owners can also schedule recurring updates from Automations.

The control is per plugin. Workspace admins must turn on "Allow use in Sites" for each one. The Business notes say: "This setting is off by default."

The Enterprise notes add a limit. Visitor access works only while someone is using the Site, and background scheduled tasks cannot reuse it. Five days earlier, on September 24, OpenAI gave Enterprise global admins a control over whether Sites can use members’ connected apps at all.

Shared Pages and Spaces with a team

Team sharing builds on ChatGPT Space, OpenAI’s new shared workspace for Pages and files. The general notes say: "Sharing in managed workspaces follows your organization’s settings; Enterprise sharing is an opt-in preview."

OpenAI’s Enterprise Space guide adds a detail to know before you test: "Disabling sharing blocks new shares and permission changes, but existing shared access remains." Turning sharing off later does not undo what staff already shared.

Before trying the preview, decide whether member data, student records and client files may go in a shared space.

Codex Cloud: shared, reusable environments

Codex Cloud lets developers start a coding task on one device and continue it on another. Each task gets its own isolated workspace, and tasks keep running while a laptop sleeps. The notes say your workspace’s Codex cloud-access settings apply.

The new part is the reusable environment. Codex installs a project’s dependencies and tools once, and you publish that setup. OpenAI’s cloud environments guide says you can share it by choosing your workspace under "Who can use," or keep it to "Only me."

Sharing the setup does not share the work: "access to the setup doesn’t grant access to someone else’s task or permission to edit the environment." Internet access is a separate setting you turn on, with a preset for package managers. Secrets go through a proxy, so programs see a placeholder.

A ChatGPT Enterprise admin at an agency should decide whether client environments stay private or shared.

Plugins and Marketplaces in the Admin console

From October 1, owners and admins manage plugins in the Admin console. Select the workspace, then open Plugins or Marketplaces. Older apps stay in Workspace settings > Apps, reached through "Manage Legacy Apps." OpenAI says existing permissions carry over.

A plugin marketplace here is a catalog of plugins you import, often from a GitHub repository. OpenAI’s plugin management guide lists two defaults every ChatGPT Enterprise admin should check:

• “New marketplaces have automatic daily sync enabled.” A plugin can change without anyone reviewing it.
• “New plugins start with Available installation.” You then set which roles get each plugin.

The guide also says: "Use a branch to receive future commits; a fixed commit stays at that revision." Pin to a commit if you want review before updates. Our Plugin4Shell post explains why pinning still needs checking.

Enterprise workspaces lose new custom GPT creation on October 26, and plugins replace them. See what moves to plugins.

OpenAI Marketplace is a buying program, not a setting

The name overlaps with the Marketplaces tab, but the two are unrelated. OpenAI Marketplace is a beta that lets eligible enterprise customers apply part of their OpenAI commitment to partner software built on OpenAI models.

There is no self-serve checkout. You contact your account team or the partner, and the partner invoices you. Most associations and colleges can skip it unless they already hold an OpenAI spending commitment.

A ChatGPT Enterprise admin checklist for this week

1. Decide on GPT-6.1 Sol and enable it in Permissions & roles if staff use Work or Codex.
2. List any workspace connections and confirm each uses a narrow, dedicated account.
3. Set who can create teams and team automations.
4. Hold @ChatGPT until you pick channels and connections, then pilot small.
5. Review “Allow use in Sites” plugin by plugin.
6. Write a sharing rule before trying Enterprise Space sharing.
7. Check Codex environment sharing and internet access on client projects.
8. Open the Plugins and Marketplaces tabs and pin commits where you need review.
9. Edu admins: confirm which items your workspace actually shows.

OpenAI’s weekly what’s new page links the setup guide for each item.

Frequently Asked Questions