OpenAI introduced ChatGPT Space and Pages at DevDay on September 29, 2026, giving teams a shared place to develop work with AI. The practical change is continuity: a report or plan can become a collaborative artifact instead of ending as a response in one person’s conversation.
A shared artifact needs a shared definition of truth
The Space product page describes living documents, real-time editing, comments, and shared context. It lists Pro, Business, and Enterprise availability, with collaborative slides and spreadsheets described as coming soon.
For a team, a useful Page should identify its owner, purpose, supporting evidence, and next decision. Otherwise, a polished document can become a repository of assertions whose origin no one remembers. Keep links to underlying sources and distinguish proposed work from decisions already approved.
Collaborative editing changes the review process
A teammate and an agent can work on the same artifact, but the team still needs to know who accepted a consequential revision. For a financial plan, product commitment, or external statement, use a clear review point and retain the evidence that supports the change.
Assign bounded editing tasks: update one section from a named source, reconcile two conflicting figures, or prepare a proposal for review. Broad instructions to “keep this accurate” are difficult to evaluate when the information comes from multiple owners with different deadlines.
Availability claims should stay specific
The launch recap separates initial Pages and Space access from planned collaborative slides. Mobile reading and sharing do not imply that every desktop creation and editing capability is already available on mobile.
Before standardizing a team process, verify the surfaces used by its actual participants. A workflow that depends on a forthcoming capability can be planned, but it should not become the only route to complete current work. Keep a reliable export or existing collaboration path where the team needs one.
Start with an evidence-based working document
A research brief or project review is a good pilot because the team can judge whether shared context makes updates easier. Track source quality, correction effort, and whether decisions are easier to locate. Avoid filling the space with automated output just to make it appear active.
The value of a shared AI workspace is that people can build on work already checked. That value depends on ownership and traceability. A document that remains useful after the original conversation ends is a stronger outcome than another impressive first draft.