Getting ready for ChatGPT collaborative slides: a team plan
This research library uses AI-assisted source research and drafting. Linked sources support product claims; analysis and proposed exercises are our interpretation. Unless an article documents a test and its results, do not read it as a hands-on review or an independently verified benchmark.
ChatGPT collaborative slides are announced but not yet available. OpenAI said at DevDay on 29 September 2026 that they arrive for Pro, Business and Enterprise in the coming weeks, according to the DevDay 2026 recap. Teammates and agents will edit the same deck at once, starting from a conversation or your own template, with export to PowerPoint or Google Slides.
There is nothing to switch on today. There is a lot to decide, though, because a deck that several people and agents edit at the same time needs clearer ownership than a deck one person builds alone.
Who needs ChatGPT collaborative slides, and who can wait?
The teams with the most to gain produce the same deck on a cadence: quarterly business reviews, sprint reviews, incident reviews, customer onboarding. They repeat structure, and the facts come from tools the agent can already read.
Teams can wait if their decks are one-off pitches or if the source material lives in systems ChatGPT cannot connect to. Plan availability is limited to Pro, Business and Enterprise. There is no separate price announced.
| Situation | Recommendation |
|---|---|
| Recurring deck with a fixed structure | Prepare a template and pilot in launch week |
| Deck built from connected tools | Pilot, with a source rule for every number |
| Board or external deck | Wait until export and review are tested |
| Deck with regulated or customer data | Wait for admin and retention documentation |
| Team not yet using ChatGPT Space | Start with Pages first, slides later |
Prepare templates before the feature lands
OpenAI says you can start slides from your own template. Use the waiting weeks to agree which template and who maintains it.
A useful team template has fixed section slides that match your review, such as goals, results, risks and decisions. It includes a sources slide at the end and a clear place for the owner's name and date. Keep it in the tool you export to today, so you can compare the ChatGPT export with the original.
Write down which slides an agent may draft and which a person must write. Results and metrics can be drafted from sources. Decisions, commitments and anything about people should come from a named person.
Review rules for decks that agents co-edit
Co-editing brings the same risks as agent-edited pages. The Space agents docs note that collaborators share content but may use different agents, connected tools or instructions. They also tell you to review an agent's changes before continuing.
We would set four rules:
- Every number on a slide traces to a source page or linked file.
- One named owner signs off before the deck is presented or exported.
- Open comments are resolved or assigned before sign-off.
- Agents may not change a slide marked as decided.
Build the source material in ChatGPT Pages first. Pages exist today, support comments and attribution, and give the deck a reviewed base.
A test plan for launch week
When slides ship, run one real recurring deck through the new flow before changing any workflow. Assign each test to a person.
| Test | Pass when | Owner |
|---|---|---|
| Template import | Layout, fonts and colours match your template | Deck owner |
| Agent draft | Every figure matches its source | Reviewer |
| Co-editing | Two people and an agent edit without lost changes | Team lead |
| Comments | Comments to people and agents route as expected | Deck owner |
| Export to PowerPoint | File opens with formatting intact | Reviewer |
| Export to Google Slides | File opens with formatting intact | Reviewer |
| Sharing | Only the intended audience can open the deck | Admin |
Formatting intact is OpenAI's claim. Your test decides whether it holds for your template.
Governance questions to settle with your admin
No admin documentation for slides exists yet. Ask these questions when it does, and do not assume the answers:
- Does the Space sharing model apply to slides, including inherited access from spaces and parent pages?
- Do saved decks follow the workspace retention policy, and can the Compliance API export them?
- Can admins restrict export to PowerPoint or Google Slides?
- Which connected tools can an agent read while drafting a deck, and under whose account?
For Space today, the admin guide says linked files keep their permissions while copied content follows the page's access. Check whether the same holds for a deck before you put restricted figures on a slide.
What to measure after rollout
Compare one recurring deck before and after. Record how long preparation took, how many corrections reviewers made, and whether any figure reached a presentation without a source. Treat a single faster deck as a signal, not a result. Our measurement guide explains how to compare fairly.
If your team wants to agree review and ownership rules for agent work across tools, our free methodology guide is a good start.
Next step: choose one recurring deck and name its owner and reviewer this week.