Rolling out ChatGPT Sites to your Enterprise team? Test connected data from a teammate's account before you share

#What changed

On Oct 15, OpenAI Developers said Sites is now generally available for ChatGPT Enterprise. Teams can build hosted apps with a database and sign-in, schedule updates, and use Plugins in Sites so each teammate sees data from their own connected apps. The same thread says new Sites in eligible workspaces get US or EU data residency, and that Enterprise workspaces can publish on their own verified domain and reach approved internal APIs through private tunnels.

The ChatGPT Sites docs back up the plugin part. A site that uses plugins reads data with each visitor's own connection and permissions, so an issue dashboard can show you your issues and show a teammate theirs. Sharing the site does not share your connected accounts.

#Who is affected

ChatGPT Enterprise workspaces where admins allow members to create Sites, and builders who want to turn a one-off Site into a team app that uses connected data such as an issue tracker or documents.

#What to do now

• Ask your workspace admin to allow plugin use for Sites. The docs say plugin use has to be enabled in the workspace, and the site has to stay private to that workspace.
• Build and preview with your own connections, then test from a second, ordinary workspace account before sharing. Your own preview does not show what another person can see.
• Enforce record access in the site's server code, not by hiding page elements. A request tracker that everyone can open should still return only each person's own records.
• Check what the site shows when a visitor declines the connection. It should explain what's missing instead of presenting an empty result as success.
• Agree on who has edit access. Editors can publish later versions without a separate owner approval.

#What is not confirmed

As of Oct 15, the docs still say custom domains aren't available in Enterprise workspaces at launch, and the Sites docs point to the Help Center for current residency coverage. Treat the residency, custom domain, and private tunnel claims as announced but not yet documented, and confirm them with your OpenAI account team before a compliance review. How scheduled updates interact with each visitor's connected data isn't described in the pages DotsFeed checked, and DotsFeed has not tested an Enterprise workspace.

#Sources

• OpenAI Developers on X: https://x.com/OpenAIDevs/status/2110832979656524283
• Custom domains and private tunnels (thread): https://x.com/OpenAIDevs/status/2110832983582371913
• ChatGPT Sites docs: https://learn.chatgpt.com/docs/sites
• Data and connections: https://learn.chatgpt.com/codex/sites/data-and-connections
• Sites administration: https://learn.chatgpt.com/codex/enterprise/sites
• Manage a site (custom domains): https://learn.chatgpt.com/codex/sites/managing-a-site