Teams give people in ChatGPT a shared place to organize work and collaborate. With Team Tasks, members can set up work to run on a schedule or when a specific event occurs, such as preparing a weekly report or summarizing new project updates.
To get started, learn how to set up a team and create a Team Task.
Enterprise admins control who can create teams and manage Team Tasks through two permissions: Create teams and Create and manage team automations. Admins can also make workspace connections available to teams. Each team’s service account and configured connections determine which external accounts its tasks use.
For more on team membership and tasks, see Teams in ChatGPT and Creating and managing team tasks in ChatGPT in the Help Center.
How teams and Team Tasks work
Workspace connections let Team Tasks use company-managed app accounts so each team member doesn’t need to connect their own account.
Teams can include people within a department or across functions who share a goal. A team in ChatGPT is separate from a workspace group created manually or synced through SCIM.
Here are examples of scheduled and event-triggered Team Tasks:
| Team | Who works together | Example Team Task |
|---|---|---|
| Product launch | Product, marketing, and support teams preparing a release. | When a message arrives in the launch Slack channel, summarize launch progress, milestone changes, and blockers. |
| Customer success | Account managers and customer success teams supporting customers. | Each Monday, summarize the previous week’s customer updates, follow-ups and open questions. |
| Sales | Sales, solutions engineers, and customer success teams closing deals and onboarding customers | When a deal closes, prepare an onboarding brief with customer goals, commitments, and open questions. |
| Marketing | Project leads and contributors responsible for a shared project. | Each morning, summarize project progress, blockers, and upcoming deadlines. |
Team Tasks run in the cloud with the team’s service account and configured app connections.
Before you begin
Before setting up a team or its tasks, a workspace owner should enable the following permissions for the intended users through workspace settings or custom roles:
-
Create teams: Required to create a team
-
Create and manage team tasks: Required to create or edit team tasks
See Roles and workspace permissions.
-
Workspace admin: Set up and authorize approved workspace connections, and choose who can find and use them. Check the external account’s data and action permissions. See Workspace connections.
-
Team owner: After creating the team, select the available connections it needs where your permissions allow. Before scheduling a Team Task, confirm which external account each connection uses.
Set up a team
-
Create the team. In the intended workspace, open Settings > Teams and select Create team. Enter a Name and optional Description, then select Create.
-
Review access and invite colleagues. Before inviting colleagues, review access to earlier runs and generated files; individual tasks and runs cannot have separate access restrictions. Select Invite, search by Name or email, and select Add member or Add members. Members can invite coworkers and remove non-owner members. Same-workspace join links do not require owner approval.
-
Add the team’s connections. Workspace connections use centrally managed accounts; team connections share an individually connected account with the team. As team owner, choose a connection you’re allowed to use. Review its data and action permissions, and complete any required sign-in before unattended work. Team ownership doesn’t grant workspace admin permissions. See Workspace connections for admin setup.
Create a Team Task
-
Open Scheduled > + New Task. Select the Team toggle and the team that will own the task.
-
Choose a Trigger. For Schedule, check the timing and time zone. For a supported event trigger, check its conditions and required connection.
-
In Instructions, describe the goal and expected output. Include success criteria and guardrails. Link task-specific sources, and review shared instructions if the team has a designated Space. Tasks do not inherit the creator’s personal memories, custom instructions, or chat history.
-
Review Plugins and Advanced settings, including Model. Choose a model available to the team; this may differ from your personal account. Select Create.
-
Select Run now and inspect the result in Previous runs. Use Edit to change instructions or settings.
Teams and Team Tasks FAQ
Can team membership be imported or kept in sync with workspace groups or Slack/Microsoft Teams channels?
No. ChatGPT team membership is separate from workspace groups and Slack or Microsoft Teams channels. It cannot be imported or synced; add and remove members in ChatGPT.
Who can create a team, change its membership, and manage its tasks?
Workspace permissions control team creation and task creation or updates. The creator becomes team owner without gaining workspace admin rights. Members can invite coworkers and remove non-owner members; same-workspace join links need no owner approval.
Only the team owner can delete the team. Workspace admins manage approved connections and who can use them.
Are these workspace controls enforced across every supported team and task creation or editing entry point?
Yes. Create teams governs team creation; Create and manage team automations governs task creation and updates across supported entry points. Team membership and connection permissions still apply.
What access does someone gain when they join a team?
New members can see all earlier runs and generated files; individual tasks and runs cannot have separate access restrictions. Pages and Spaces retain their own sharing permissions. Joining a team, you’ll inherit any pages and spaces that are shared with the team. Joining does not share personal chats or connections. Workspace members opening a join link can see the team’s name and member list before joining.
How can workspace admins review activity without joining a team?
Admins can review activity through the Compliance API and restrict access by role.
Whose account does a Team Task use?
Team Tasks use the team’s service account and configured app connections. A connection’s account determines its data and actions, which may differ from the creator’s or editor’s personal access. See Connecting and managing app accounts.
How do plugins and connections work together?
Team plugins and connections serve different purposes: plugins provide tools or skills; connections supply app access. Members need not connect the same account individually.
Can workspace connections expose information beyond a member's personal access?
Yes. Connected accounts may access information a member’s own account cannot. Review team membership alongside each connection’s resource access.
Can Team Tasks write to connected systems?
Yes, if the tool and connection allow it—for example, posting to Slack. Unattended runs cannot complete a new app sign-in and remain subject to action-approval requirements.
What happens when a task creator or team owner leaves?
Authorized teammates can edit, pause, or resume shared tasks. Before offboarding a creator or owner, review team ownership and required connections.
Team-owned tasks are designed to persist after the creator leaves, but required connections may lose access.
Owners must transfer ownership before leaving. Connections the new owner cannot access become disabled for the entire team.
What happens to active and queued runs when a task is paused or deleted?
Pausing prevents future scheduled and event-triggered runs. Neither pausing nor deleting a task should be relied on to interrupt an active run.
What team and task activity can admins audit?
The team’s Activity view keeps track of changes. Authorized members can inspect individual runs and results.
Use supported Compliance API records to investigate team activity. Confirm which team, task, and connection records are available before relying on them for an audit.
Use the current Admin API reference for each event’s exact fields and supported coverage.
How are Team Tasks billed?
Team Tasks use workspace credits. Team spending limits are separate from user limits.