Updated 10 hours ago
ChatGPT Space replaces Library for eligible users, while Projects stay separate

OpenAI DevDay

ChatGPT Space replaces Library for eligible users, while Projects stay separate

OpenAI's DevDay launch gives teams a shared home for pages and files. The current help guide draws important lines around Projects, mobile editing, inherited access and automatic page updates.

The new home is for pages and shared work, not your Project chats

OpenAI introduced [ChatGPT Space at DevDay on September 29](https://openai.com/index/devday‑2026‑recap/) as a place where teammates, ChatGPT and a dot can build on shared knowledge. Its more detailed [getting‑started guide](https://help.openai.com/en/articles/20001549‑getting‑started‑with‑space‑in‑chatgpt) makes the migration narrower than the name may suggest: Space replaces Library for accounts that have access to Space, while Projects continue separately for project chats, files and instructions. A team moving a brief into Space should not assume its existing Project conversations or setup have become shared documents. A space groups pages, uploaded files and folders; a page can also have subpages. OpenAI says people can start a page from a conversation, edit it directly or ask ChatGPT to revise it. Teammates with edit access can work on the same page and leave comments. That makes Space a destination for an evolving document rather than a new model or a replacement for every way ChatGPT organizes work. For a team launch plan, the useful distinction is to keep discussions in Projects where appropriate and put the brief, decisions and handoff material in pages that collaborators can actually find.

Sharing a page does not grant access to every file it mentions

The [Space help guide's access rules](https://help.openai.com/en/articles/20001549‑getting‑started‑with‑space‑in‑chatgpt) are consequential for a team adopting it. A file uploaded into a page follows that page's permissions. A link to a file stored separately in Space or in a connected service does not give the page's readers access to the original file; that service keeps its own permissions. But text copied or summarized from the source onto a shared page is visible to anyone who can view the page, even if those people could not open the original. A practical pre‑share check is therefore both who can see the page and what information the page itself now contains. Access can come from a direct page invitation, its parent page or its space. The guide says subpages inherit parent access, so removing one direct invitation may not remove access granted higher in that chain. It also says sharing a page does not expose a teammate's private chats or ChatGPT Memory, but information brought from memory into the shared page becomes visible to its readers. Managed‑workspace settings still govern the sharing options available. Those boundaries matter more than the general promise of a shared workspace when a team is handling client or internal material.

Desktop creation is here; mobile editing and some workspaces must wait

The launch recap lists Space for Pro, Business and Enterprise on the ChatGPT web and desktop apps. The current help page says mobile users can find, read and share pages, but cannot create or edit them yet. It also says Business and Enterprise workspaces with data residency in Canada or the United Arab Emirates are coming later, and that managed sharing can require administrator enablement. A plan name alone is therefore not a reliable test that every teammate has the same creation and collaboration controls today.

OpenAI's Space product page describes pages that can stay current from connected tools and gives an example of scheduled automation. The more specific help guide says the automatic Keep updated page feature is not available at launch. A person can still ask ChatGPT to revise a page and, where an automation is available, configure a separate recurring task; that should not be described as the unreleased automatic page‑update control. OpenAI also marks collaborative slides and spreadsheets as coming soon. Teams planning a workflow now should design around editable pages and current permissions, then revisit those promised features when their accounts actually receive them.

A migration check begins with the real reader and the real permission

A small trial can start with one page in a personal or team space: bring over a non‑sensitive brief, invite a collaborator with the intended view or edit access, and verify that they can open every linked source they need. The [guide's page and Space instructions](https://help.openai.com/en/articles/20001549‑getting‑started‑with‑space‑in‑chatgpt) explain how to organize a parent page and subpages, while the access rules explain why a linked document and a copied summary have different exposure. This is a decision about document location and sharing, not evidence that ChatGPT has independently checked the facts on a page. Space is a new part of [ChatGPT](https://opentools.ai/tools/chatgpt), made by [OpenAI](https://opentools.ai/organizations/openai). The immediate question for a team is which pages should be shared, with whom, and on which device they need to edit. Keeping Projects distinct and testing inherited access avoids a confusing migration from Library while the broader Space rollout continues.

Share this article

PostShare

Related News