OpenAI Adds Shared Team Tasks to ChatGPT Business
Workspace teams can jointly maintain recurring tasks and use admin-approved connections, while Slack and Microsoft Teams become controlled collaboration entry points.
Edited by Tyronne Panaino
OpenAI added shared team tasks to ChatGPT Business on September 29, allowing authorized coworkers to review results, update instructions and maintain recurring work that runs on a schedule or supported trigger. The same release group makes @ChatGPT available inside Slack and Microsoft Teams for Business organizations that install and enable it.
The change matters because recurring AI work no longer has to depend on one person remaining available to maintain it. OpenAI's ChatGPT Business release notes describe a team-level workflow, but they also keep the access boundary explicit: workspace permissions, administrator configuration and the connected provider account still determine what the task can reach and do.
Recurring work becomes team-maintained
OpenAI says team tasks let coworkers share responsibility for recurring work in ChatGPT. An authorized teammate can review results and revise the instructions used for later runs, reducing the operational dependence on a single creator. Tasks can use a schedule or a supported trigger and can work with company tools that the organization has approved.
The release also adds a broader team container. Colleagues can share Pages or Spaces, use shared plugins and maintain recurring tasks together. Those capabilities remain subject to workspace permissions. Team membership does not automatically expose a member's personal chats or personal app connections, and it does not override the organization's existing access controls.
That distinction is the practical delta from simply forwarding one person's automated output to a group. The task itself becomes maintainable by the team, while private account context does not automatically become team context.
Connections and plugins remain separate controls
ChatGPT Business administrators can configure app connections for teams. A team owner can then enable eligible workspace connections, so every teammate does not need to connect the same provider account separately. OpenAI says the permissions of that provider account determine which information and actions a task can access.
OpenAI also separates plugin sharing from connection access. A shared plugin does not by itself grant access to the app account behind it. For administrators, that means reviewing the plugin is only one part of the control model; the enabled connection and the provider account's permissions are the operative access boundary.
A sensible deployment review should therefore identify the team that owns each recurring task, the provider account behind every enabled connection, the information that account can read and the actions it can take. That is an editorial recommendation derived from OpenAI's permission model, not evidence that the controls have been independently tested.
Slack and Teams are entry points, not permission bypasses
OpenAI says @ChatGPT is now available for ChatGPT Business in Slack and Microsoft Teams. Members can message it directly or mention it in an enabled channel to ask questions, summarize discussions or draft work with teammates.
The organization must install and enable @ChatGPT before members can use it. Administrators configure its instructions and connections, and the connected accounts determine which company resources and actions are available. The collaboration app therefore provides another place to start work; it does not replace the permission checks attached to the ChatGPT workspace and connected accounts.
What remains unverified
The release notes establish the dated product change, the shared-maintenance model and the stated permission boundaries. They do not provide independent evidence about tenant-level rollout completeness, task reliability, output quality or the accuracy of actions taken through connected tools. Those questions require observation inside real Business workspaces.
The next useful checkpoint is whether administrators can consistently audit team ownership, enabled connections and task results across ChatGPT, Slack and Microsoft Teams. Until operating evidence is available, the supported conclusion is narrow: OpenAI has added shared team maintenance and collaboration entry points, with access still bounded by workspace and provider-account controls.
Status
Confirmed product and workspace-governance change; medium internal confidence. The evidence is one official OpenAI release-note page, and this run did not independently test availability or operation in a Business tenant.
Sources
Update note: Last reviewed 2026-10-01. We will revise this post if OpenAI changes availability, team ownership, connection permissions or collaboration-app behavior.
Sources
- OpenAI — ChatGPT Business release notes — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.