ChatGPT Enterprise and Edu Updates: Codex, Team Tasks

OpenAI’s September 29 ChatGPT Enterprise and Edu release notes bundle a shift toward shared, persistent work: authorized Enterprise members can reuse cloud environments for Codex tasks, and teams can maintain recurring tasks together. But these features are governed by workspace settings and connected-account permissions, so they do not make every tool or action available to every member.

Codex tasks can outlive a local session

Enterprise members with the required access can share reusable Codex Cloud environments and start or continue tasks from desktop, web or mobile. Each task gets an isolated workspace and can keep running while the member’s computer is asleep. Enterprise cloud-access settings still apply. OpenAI lists these Codex Cloud changes in the September 29 entry.

The useful distinction is between sharing an environment and sharing a task’s access to company data. The release notes say each task has its own workspace, but access to connected tools remains governed separately. That separation matters for teams: reusable setup can reduce repeated configuration without implying that everyone inherits the same permissions.

OpenAI is also rolling out GPT-6.1 Sol in ChatGPT Work and Codex, starting with Pro users and expanding to Plus, Business, Enterprise and Edu. The company characterizes the model as an improvement over GPT-6 Sol in agentic coding, computer use and professional work. Enterprise and Edu administrators must enable access, and the release notes provide no independent benchmark results for those claims.

Recurring work gets shared ownership

Enterprise teams can set tasks to run on a schedule or supported trigger using approved company tools. Authorized teammates can review results and update instructions together. OpenAI’s example is a weekly project update sent to an approved Slack channel. Team-task availability is subject to workspace permissions.

Administrators can configure eligible app connections for teams, allowing a team owner to enable a provider connection without asking every teammate to connect the same account. The connected provider account still determines what information and actions a task can access. Sharing a plugin and granting access to an app connection are separate controls, a useful boundary when tasks become routine rather than one-off.

ChatGPT can also be used through @ChatGPT in Slack and Microsoft Teams for Enterprise. Members can ask questions, summarize discussions or draft work in enabled contexts. Admins configure its instructions and approved connections; replies in shared conversations are visible to participants. The integration follows connected-account permissions, so the chat surface does not bypass existing access rules.

Sites and Marketplace come with conditions

Enterprise and Edu Site owners and editors can continue editing a published Site in a desktop browser. Owners can create recurring cloud schedules, and private Sites can use supported connected apps. However, organization approval is required, administrators must turn on “Allow use in Sites” for each plugin, and that setting is off by default. Visitor access while using a Site cannot be reused by background scheduled tasks. The Sites update retains existing permissions and regional availability.

OpenAI also announced Marketplace in beta, where eligible enterprise customers can apply part of their OpenAI commitment toward qualifying partner software. Eligibility is assessed for each customer, product and purchase. Customers contract with and receive invoices from the partner; they can browse and express interest, but there is no self-service checkout. The beta is a partner purchasing route, not a universal credit balance or in-product store.

Across the release, the pattern is consistent: shared workflows are becoming easier to configure, but sharing does not erase boundaries around data access, workspace policy or who can approve a connection. That makes administrative setup part of the feature itself, not an afterthought.