ChatGPT Space: Create a Page, Share It and Keep It Useful
ChatGPT Space helps turn conversations, notes and files into shared work you can revisit and edit. Start with one page that answers a real question—such as what your team needs to publish this week—then check the facts and permissions before expanding the workflow.

Documentation reviewed November 13, 2026. The image is conceptual, not a product screenshot; the workflow below is an example, not a measured productivity study.
Contents
- Space, a space and a page: what is the difference?
- Create your first page
- A useful weekly brief, with a clear review step
- Share the information, not just a link
- If Space or an action is missing
- FAQ
Space, a space and a page: what is the difference?
Your workspace is the account or organization environment. Space brings saved work together; a space groups related pages. A page is an editable document, with optional child pages. The official overview also describes slides, spreadsheets, sites and files. The older claim that collaborative slides are merely forthcoming is no longer current.
Use a conversation to explore a question and a page to maintain an agreed version of the answer. A page is useful when another reader needs the current decision without replaying the whole chat.
Create your first page
An account with Space enabled is required. Follow the getting-started guide, then use this bounded pilot:
- Open Space in the intended account and select New page. Name it “Editorial brief — week of November 16.”
- Add the relevant notes, files or source links. Specify which source governs dates and approval status.
- Ask ChatGPT to draft the brief using the prompt below. Review it on the page.
- Check important facts against sources, then invite one reviewer with the intended access.
Create a weekly editorial brief from these sources. Include decisions needed, work in progress, blockers and next actions. Record owners and dates only when stated; otherwise use “Unassigned” and “Date not confirmed.” Link claims to evidence. Keep proposals separate from approved decisions. Do not mark work complete merely because a draft exists.
The page editor supports direct edits and an insert menu opened with /. Add a table or checklist only when it clarifies a decision. This prompt is a starting template, not a guarantee of factual accuracy.
A useful weekly brief, with a clear review step
| Section | What belongs there | Acceptance check |
|---|---|---|
| Decisions | Questions blocking publication | A reviewer knows what must be decided |
| Work | Article, owner, status, next step | Status is supported by evidence |
| Sources | Links and review dates | Important claims can be checked |
| Open issues | Missing or conflicting information | Uncertainty stays visible |
For a narrow change, select text or use a comment where offered. For a broader change, use the conversation alongside the page. The agent guide explains these entry points and notes that availability depends on access.
Try: “Update only Open issues using the new notes. Preserve approved decisions and links. Show conflicting claims rather than choosing silently.” Afterward, compare the affected section with the notes. Mentioning someone does not establish that they accepted an assignment.
For model selection background, see our GPT-6 Astra guide. Model access and permission to collaborate in Space are separate checks.
Share the information, not just a link
The sharing controls distinguish direct and inherited access. Removing a direct invitation may leave access through a parent page or space. A linked external file keeps its own permissions, but information copied into a page is visible to that page's audience.
Before wider sharing, test a reader, an editor and someone whose access should be removed. Check the child pages too. Avoid pasting a restricted source's sensitive summary into a broadly shared brief simply because its original link remains restricted.
Adding a source does not by itself create a refresh schedule. For a recurring brief, explicitly define when to run, which sources to read, what section may change and who reviews it. Confirm a run succeeded and produced the intended update before relying on automation.
If Space or an action is missing
Confirm the signed-in account and workspace first. Check whether the needed action exists on web or desktop, and ask an organization administrator about access or sharing restrictions. A plan name or an old rollout post is not proof that your account has every control.
If a colleague cannot open a page, inspect the invitation identity and inherited access. If they cannot open a source, check that source's permissions separately. If an AI edit changes approved facts, restore the correct content and repeat with a smaller scope and explicit source requirements.
FAQ
Is Space included with ChatGPT Plus?
The current getting-started documentation requires Space to be enabled but does not establish universal eligibility by plan. Check your account and current offer before upgrading solely for Space.
Can I use slides or mobile?
Current guidance documents collaborative slides. On mobile, it describes creating slides through conversation and viewing decks; direct slide-element editing uses web or desktop. Check your exact page-editing workflow separately rather than assuming identical controls everywhere.
Will connected files update the page automatically?
Not simply because they are connected. Source access, a scheduled task, successful execution and human review are separate parts of a reliable recurring workflow.
