In ChatGPT Space, removing someone's invite to a page leaves any access they inherit from a parent page or Space untouched, so check the parent before assuming they can no longer read it. OpenAI's own collaboration docs say so, and the rest of the sharing model follows from it. Space puts a page workspace inside the ChatGPT Business and Enterprise seats you already pay for, and it costs nothing extra. The cost shows up later, in access reviews, in what summaries expose, and in the export path you will want once a team has moved its notes in.
Treat Space as a shared drive with an agent attached, and make this quarter's decision about which teams get it and under what sharing settings.
What Is ChatGPT Space, and What Does It Cost?
ChatGPT Space is a shared workspace of pages and files that people and ChatGPT's agents work from as common context. InfoQ's DevDay 2026 write-up describes it as "a shared workspace where teams and agents can work with common context." The Decoder reports it is available on Pro, Business and Enterprise on desktop and web, with members dropping in files and projects that the new Dot assistant draws on to answer questions and hand off work.
A page is the unit of work. OpenAI's getting-started guide says you can "start with a blank page, notes you already have, or a conversation you want to save," and group related pages into a Space by topic or team. Space also takes over from Library: an independent walkthrough notes that "Space replaces Library for Pro, Business, and Enterprise users."
On price, eesel's launch explainer notes: "There's no separate price for Space. It isn't a line item on the ChatGPT pricing page." OpenAI's pricing page lists Business at $20 per user per month billed annually (two-user minimum) or $25 monthly, with Enterprise priced through sales. Nothing OpenAI has published commits to keeping Space unpriced, so put that question to your account team now rather than at renewal.
How Does Access Inheritance Work in Space?
Access in Space flows downward and is only removed where it was granted. OpenAI's collaboration docs say that "access to a shared Space applies to its pages," that sharing a page also grants access to its child pages, and that the interface separates "direct access from access inherited from a parent page or Space." The roles are View, Comment and Edit.
The sentence an access reviewer needs is this one, from the same page: "Removing a direct invitation doesn't remove access that someone still inherits from a parent page or Space." To actually cut someone off, OpenAI tells you to "review the parent or Space's sharing controls."
Anyone who has run SharePoint or Google Drive permissions will recognise the pattern. Inheritance is convenient on the way in and easy to miss on the way out. A team lead shares the "Q4 Planning" Space with a contractor, later invites them directly to one page, then removes that invite when the engagement ends. The contractor still reads every page in the Space.
The admin kill switch has a similar gap. OpenAI's enterprise admin page for Space says disabling sharing "blocks new shares and permission changes, but existing shared access remains." Turning sharing off stops the problem from growing. It does not undo what is already shared, so a cleanup has to happen page by page or Space by Space.
Why Do Linked-File Summaries Matter More Than Linked Files?
Linked files keep their own permissions, but anything summarised or copied onto a page belongs to the page. The collaboration docs note that "a collaborator who can read your page may still lack permission to open a source linked from it." That is the reassuring half.
The other half is on the enterprise admin page: "Content copied or summarized onto a page is visible to its collaborators." eesel's review spells out the effect: a file linked through a connector keeps its permissions, "but anything you or ChatGPT copied or summarized from that file onto the page is readable anyway."
In practice, a finance analyst links a restricted board deck from Google Drive, asks ChatGPT to summarise the revenue bridge onto a page, and shares the page with a 40-person ops channel. The deck stays locked. The numbers are now on a page 40 people can read. No permission was broken, because the summary is a new piece of content with the page's permissions. Your DLP rules were probably written for files moving between systems and will not see this.
This is the same problem enterprise search buyers already price in: permission sync is where those tools differ, and Space's model resets permissions at the point of summarisation.
What Isn't Live Yet?
Several things a wiki owner would expect are missing or unannounced at launch. The two reviews that read the docs most closely agree on the gaps:
- Export and version history. eesel's launch explainer says pages "have no export or version history yet." A Space vs Notion comparison found that OpenAI's getting-started, Pages, Agents and Collaboration docs, checked on September 30, 2026, do "not document an export command or migration format." The one documented path out is administrative: the enterprise admin page says Compliance API permissions are needed to "export or delete eligible saved Library files," and that "an Admin role alone does not grant sensitive compliance access."
- Data residency in Canada and the UAE. eesel's review lists Space as not available at launch for "Enterprise and Business workspaces with data residency in Canada or the United Arab Emirates," with support marked "coming soon."
- Enterprise sharing maturity. The launch explainer says Enterprise sharing is in "opt-in preview" and "runs on the old Library sharing controls," while Business admins can "switch Space off for the workspace."
- Mobile editing, self-updating pages, slides and spreadsheets. Each is listed as coming later in the same reviews.
Reliability is also unproven. eesel's review records a status-page incident within hours of release: "errors creating or interacting with Pages, including failures when using Page tools or connecting to live Page sessions." One launch-day incident says little on its own. It is a reason to keep anything a team cannot work without somewhere else for now.
OpenAI's history with collaboration features adds to the caution. The Decoder notes the company previously experimented with shared chats between multiple users and AI and "shut that feature down in July, saying it wanted to keep ChatGPT simpler." Without a documented export, a reversal on Space would cost more.
Can Space Replace Confluence or Notion Pages?
Not yet for any page set you have to audit, migrate or keep. Space is a reasonable home for working drafts a team builds with ChatGPT; it falls short as a system of record.
The fairest case for Space is strong. It costs nothing extra for a tenant you already license, it sits where your staff already work with ChatGPT, and the agent reads the pages directly, with no connector to configure. For a team whose real workflow is "draft in ChatGPT, paste into the wiki," removing the paste step is a genuine gain.
Compare the exit, though. The same comparison notes that Notion can export pages and databases as PDF, HTML, Markdown or CSV, and a whole workspace as HTML, Markdown or CSV with uploaded files, at $20 per member per month annually on Notion Business. Space has no documented equivalent today. Confluence and SharePoint also carry page history that your auditors may already rely on.
If your search layer already indexes Confluence or SharePoint through something like Glean, moving pages into Space also moves them out of that index unless a connector catches up. Check that before a team migrates, the same way you would for any knowledge tool swap.
What to Do Before You Turn It On
This Week:
- Find out whether Space is already on. It replaces Library on Business and Enterprise, so check the workspace settings and the "Share Library files and folders" controls described on the enterprise admin page before users start sharing.
- If your workspace has Canada or UAE data residency, write down that Space is unavailable there and tell any team that asks.
- Restrict sharing by role to a pilot group. Disabling it later will not claw back existing shares, so the starting setting is the one that counts.
This Month:
- Write a one-paragraph rule for summaries: no summarising restricted files onto pages shared beyond the file's own audience. Send it to the pilot group in plain words.
- Add Space to your access-review procedure. Reviewers must check parent pages and Space-level sharing, because removing a page invite alone leaves inherited access in place.
- Confirm who in your org holds Compliance API permissions and test whether they can export a sample page. If the answer is no, record that as a known gap.
Before You Retire Any Wiki Pages:
- Get in writing from OpenAI whether Space stays at no additional cost, and when export and version history will ship.
- Keep Confluence, Notion or SharePoint as the system of record for policies, runbooks and anything an auditor reads, until Space has a documented export.
The Bottom Line
Space follows the pattern of collaboration tools bundled into a suite seat, where adoption runs ahead of governance. SharePoint and Google Drive both taught admins to review sharing from the top of the tree down. OpenAI has documented the sharing rules clearly, which helps. The rules mean a removed invite and a disabled sharing setting both leave existing access in place, so your controls have to run at the Space and parent-page level from day one.
This is the third DevDay launch that lands in the tenant you already pay for, after @ChatGPT in Slack and Teams and the Dots beta. Each widens who can see what inside ChatGPT. Pilot Space with one team, set sharing by role first, and put the parent-page check into this month's access review.
Continue Reading
- @ChatGPT in Slack and Teams Gives Unlicensed Staff a Shared Account
- OpenAI's Dots Beta Skips Data Residency and Your OTel Collector
- Glean Alternatives: Price the Permission Sync, Not the Seat
- Glean vs Copilot vs Dust: Buy the Permission Model
- RAG Build vs Buy: Buy the Index. Build the Eval Set.
- Mitratech Buys BotDojo, Whose Terms Offer No Data Export