ChatGPT Sites Adds Teammate Editing, External Viewers, and Public Publishing Controls

OpenAI added teammate editing and broader sharing controls to ChatGPT Sites, turning Sites from a mostly single-owner workflow into a shared workspace surface. In an approved OpenAI post on X, OpenAI describes the update as a major expansion of creating, sharing, and hosting Sites directly through ChatGPT. The official ChatGPT Sites documentation now makes the concrete permission boundaries clear: workspace editors, named external viewers, and public publishing are separate access paths.

The official ChatGPT Sites help page defines the permission boundary: a Site owner can give an active member of the same workspace Can edit access. That editor can change and save the Site, but the publishing sequence matters: the owner must publish the Site once before an editor can publish later versions to the same URL.

This is a narrower collaboration model than handing over ownership. The owner keeps control over the audience, Site identity, ownership transfer, secrets, and custom domains, while the editor gets the part of the workflow that benefits from parallel work: updating the Site and saving reviewed versions.

Key Takeaways

• Owners can add workspace teammates as editors with Can edit access.
• Editors can update, review, and save the shared Site.
• The owner must publish first. After that, editors can publish later versions to the same Site URL.
• Editors do not need separate owner approval for those later publishes.
• The owner retains control over access, the Site name and URL, ownership transfer, secrets, and custom domains.
• Named external viewers are view-only. They must sign in with the invited account and cannot edit or publish.
• Public publishing is controlled by plan and workspace settings. Enterprise workspaces keep public publishing off by default until an administrator enables it.
• This is a ChatGPT workspace feature, not an invitation to treat a public Site URL as an editable project.

What the Latest Sites Update Adds

The new Sites controls separate three collaboration and distribution jobs that are easy to conflate:

1. Workspace co-editing: an owner grants an active member of the same workspace Can edit access. The editor can update, preview, and save the shared Site.
2. Named external viewing: an owner can invite someone outside the workspace as a viewer where the account and workspace support it. The viewer signs in with the invited account, but cannot edit or publish and does not automatically get access to other workspace content.
3. Public publishing: a Site can be published for anyone on the internet only when that option is available and enabled. In Enterprise workspaces, public publishing is off by default and requires administrator enablement.

The OpenAI Help Center also warns that Sites is in public beta for eligible ChatGPT workspaces, Plus, and Pro accounts. Rollout, plan-specific limits, and workspace controls affect what an account can create, store, publish, or share. A beta limit can temporarily block new Sites, additional storage, or continued public availability for a high-usage Site while leaving existing Sites editable and manageable.

One operational detail matters when a team is shipping changes: ChatGPT treats every deployment URL as a production URL. Review a version before deploying if you do not want to update the live Site. (OpenAI Help Center)

How ChatGPT Sites Co-Editing Works

The collaboration model starts with an existing Site and an active member of the same ChatGPT workspace. The owner opens Share, selects the teammate under Who has access, and changes that person’s access to Can edit. The workspace help page confirms that the editor permission is granted by the Site owner and applies to an eligible active workspace member. (OpenAI Help Center; OpenAI workspace guidance)

After access is granted, the editor can open Sites, choose Shared with you, open the Site, make changes, review the updated preview, and save a version. This keeps the editor in the same Site workflow rather than creating a fork that the owner has to manually reconcile.

The permission is specifically Can edit, not an unrestricted transfer of the project. The owner can later change the editor to Can view or remove them; whether that person can still view the Site then depends on the Site’s remaining audience settings. (OpenAI workspace guidance)

The First-Publish Rule

The most important operational detail is the first-publish gate. An editor can update and save a Site before the owner’s first publish, but the official help page says the owner must publish the Site once before an editor can publish later versions to the same Site URL. Once that first publish is complete, the editor can publish subsequent versions without a separate owner-approval step. (OpenAI Help Center)

That sequence separates initial ownership and launch approval from ongoing iteration:

1. The owner creates the Site and grants Can edit access to an active workspace member.
2. The editor opens the shared Site, makes changes, reviews the preview, and saves a version.
3. The owner publishes the Site for the first time.
4. The editor can publish later versions to the same URL as the team continues to work.

For teams, this means the first publish is the point to settle the audience and content review process. Once the Site is live, an editor can ship an approved change without asking the owner to click publish every time.

What Stays With the Owner

Co-editing does not make every Site setting collaborative. According to OpenAI’s help documentation, only the owner can:

• Manage who has access.
• Change the Site name.
• Change the Site URL.
• Transfer ownership.
• Configure owner-only settings such as secrets and custom domains.

That division is useful for teams sharing a Site that contains a live workflow or internal tool. Editors can improve the content and interface, while one accountable owner retains control of identity, access, credentials, and the URL. (OpenAI Help Center; OpenAI workspace guidance)

When to Use Teammate Editing

Teammate editing is most useful when a Site is a shared deliverable rather than a personal experiment:

• A launch calendar: one person establishes the structure while marketing and product teammates refine copy and links.
• An internal portal: a workspace owner controls access and custom-domain settings while subject-matter experts keep pages current.
• A review workspace: an analyst publishes the first version, then collaborators update charts, notes, or decisions as the work progresses.
• A lightweight prototype: a builder creates the first Site and teammates test flows, suggest changes, and save the next version.

The important distinction is that the Site remains a shared artifact with a single owner, not a fully ownerless document. Use the owner-only controls to establish who can access it and how the published URL should be managed.

Availability and Workspace Caveats

The official Sites documentation describes Sites as available in public beta for eligible ChatGPT workspaces, Plus, and Pro accounts, with rollout and workspace settings affecting access. Business workspaces have Sites enabled by default, while Enterprise administrators can control who can create and publish Sites through role-based access controls. Public publishing in Enterprise is off by default and requires administrator enablement. (OpenAI Help Center; OpenAI workspace guidance)

Those controls apply to the Site and its workspace, not just to the individual editor. If Can edit or Shared with you is missing, OpenAI says co-editing may not yet be available for the account; a workspace owner or administrator may need to confirm that the relevant Sites permission toggles are enabled. (OpenAI Help Center)

Bottom Line

ChatGPT Sites now supports a practical team handoff and a more granular sharing model: an owner grants a workspace teammate Can edit, the teammate updates and saves the Site, and—after the owner’s first publish—can publish later versions to the same URL. Owners can separately invite named external viewers without making the Site public, while public publishing remains subject to plan and workspace controls. The owner still controls access, identity, ownership, secrets, and domains, so teams get collaborative iteration without losing a clear authority boundary.

Sources

• OpenAI Developers on X, “Add teammates as editors to your ChatGPT Sites” (August 20, 2026): https://x.com/OpenAIDevs/status/2090515079058108745
• Tibo on X, quoting ChatGPT’s Sites update (September 12, 2026): https://x.com/thsottiaux/status/2098569538510180712
• OpenAI Help Center, “Creating and managing ChatGPT Sites”: https://help.openai.com/en/articles/20001339-creating-and-managing-chatgpt-sites
• OpenAI Help Center, “ChatGPT Release Notes” (September 3, 2026): https://help.openai.com/en/articles/6825453-chatgpt-release-notes
• OpenAI Help Center, “Managing ChatGPT Sites for your workspace”: https://help.openai.com/en/articles/20001338-managing-chatgpt-sites-for-your-workspace