Using ChatGPT Space: access, sharing permissions, and collaboration plans

What is Space, and where do I use it?

ChatGPT Space combines pages, files, and shared work for plans, meeting notes, or team material. A Page is a collaboratively editable document: edit text yourself or ask adjacent ChatGPT to rewrite, expand, or explain it. A lowercase space organizes related pages by topic/team. Neither is the same as your personal or organization account workspace.

Getting-started documentation requires Space already enabled on your account. In Space, use All for saved work or Your items, Shared with you, and search. Choose New page or ask ChatGPT to turn a conversation into a Page. These are documented entry points, not a substitute for checking your actual logged-in account’s access.

Eligibility involves account and organization settings, not just a plan name

September 29, 2026 release notes describe existing Pages/Space for eligible Pro, Business, and Enterprise users in desktop/web ChatGPT. Eligible cannot be omitted: this does not promise an entry point for every account with that plan, or list Free, Go, or Plus as covered here.

Organization sharing follows organization settings. Enterprise sharing is an opt-in preview. If sharing is absent, check account, workspace, and visible permissions, then ask an authorized administrator. The documentation does not promise identical iOS/Android/desktop features; buying or changing plans is not an immediate unlock of every collaboration option.

Space and Projects are separate: do not mistake an old project for the new entry

The same release says Space replaces Library for accounts with access, while existing Projects remain separate. Space emphasizes organizing Pages, files, and shared content. Seeing Projects or a shared-project link does not establish Space access; check project chats, sources, and permissions in their own entry points.

Define the output first: for an editable discussion page with reviewers, use Page/sharing; for a problem in an existing Project, retain its link, account, and workspace. Do not delete projects to find Space or treat recovery of a shared-project incident as proof Space works.

Start with a non-sensitive Page, then build a collaborative space

Create a clearly titled Page containing notes, files, or links you may use. Ask adjacent ChatGPT to organize it, specifying facts to retain and questions still unresolved. Inspect edits on the page before sharing; a generated draft does not verify facts.

For related pages, the official flow is All → New → Space, enter topic/team name, optionally expand Invite people, then create. Inviting someone to a space grants access to that group of pages. Use the page’s sharing controls for only one page. Check contents before inviting because the scopes differ.

Before sharing, inspect roles, inherited access, and source permissions

Collaboration documents list View, Comment, and Edit for reading, feedback, and changes. Available choices depend on account, workspace, and recipient; a Team invitation may offer only view/edit. Add permitted people or Teams, choose access, save, and have collaborators confirm the expected access.

Sharing a space applies access to its pages; sharing a parent page grants access to child pages. Removing a direct invitation may leave inherited access from a parent or space. Inspect direct and inherited origins when revoking access rather than assuming one removed invitation hides the content.

Sharing does not automatically expose private chats or saved memories, but copied/summarized private material on the Page is visible to authorized collaborators. External source files retain original permissions: reading a Page does not grant its linked files. Inspect page text and source access before sharing; private chats remaining private does not hide summaries copied onto a page.

October 5: refinement commitments, not confirmation of every fix

At 20:05:31 UTC on October 5, 2026—04:05:31 Beijing time October 6—Tibo said Sergio was advancing collaboration spaces and the experience was improving. He quoted Sergio’s Space post, visibly last edited18:54:09 UTC October 5. Its original publication time was not verified; editing time is not first publication. Sergio’s public bio says Codex App @OpenAI.

Responding to issues such as tagging a Dot without a response, Sergio said at 20:07:19 UTC that they would refine quickly and the fundamentals existed. At 19:07:33 UTC he would examine tagging and make human/dot interaction more intuitive. At 20:31:35 UTC he said iOS/macOS read/write consistency was being addressed. These attributed directions and responses deserve follow-up but do not announce individual deployed fixes or dates.

Current Pages documentation permits @ references to people, agents, files, or chats, and mentioning ChatGPT in comments with a request. It does not guarantee every mention of any Dot executes immediately. These Space replies were not labeled as a delivered day in Tibo’s28-day pledge; do not add that attribution.

For different phone/computer behavior, record location and outcome

If mobile permits viewing but not editing, or a mention fails to respond as expected, record whether it was a Page, comment, or invitation, plus account, workspace, app version, and time. Check for existing changes. Use a non-private page to inspect entry points/permissions rather than repeatedly testing formal team material. This article did not test cross-device behavior or verify a fix in any version.

For access issues, verify account/workspace and saved Page/space permissions. Ask someone authorized if you cannot edit or manage sharing. When an agent edits shared work, specify paragraphs and team decisions to preserve. Inspect existing content before resubmitting an uncertain change.

How to follow actual future changes

Follow dated release notes, Space docs, and original owner posts separately. Mark a capability delivered only when a new announcement explicitly says so; being worked on remains a plan. Retain account/organization conditions when checking access; another user’s screen does not establish universal eligibility.

This page distinguishes September 29 features from October 5 public improvement directions. Fix dates, consistent cross-device editing, and each account’s access remain uncertain. It does not infer extra allowances, automatic execution promises, or completed migration for all teams.