ChatGPT Adds Shareable Profiles as Sites Gain Connected Plugins
ChatGPT's new shareable profiles showcase your Sites and activity, while Sites gain connected plugins so teams share apps with individual permissions.
By Dillip Chowdary • Sep 30, 2026 • Source: OpenAI
OpenAI added a social layer to ChatGPT at DevDay 2026: shareable profiles — private or public pages that showcase a user's Sites and activity — are rolling out gradually, with Enterprise support to follow. In parallel, Sites, ChatGPT's shareable web properties, gained connected plugins and integrated data, so a site is no longer a static artifact: team members can use the same site-hosted app while each operates under their own account, data access, and permissions.
This piece covers what profiles and upgraded Sites are, why per-user permissions turn Sites from pages into software, how the pair fits OpenAI's platform ambitions, and what builders and admins should note. It is written for developers, creators, and workspace owners watching ChatGPT become a distribution surface.
Profiles and Sites: what launched
A profile is the identity anchor: a page, private or public at the user's choice, displaying the Sites they have built and their activity. The launch imagery showed exactly that shape — a person's page with activity and showcased creations. Rollout is gradual rather than universal, and Enterprise support is explicitly marked as coming rather than present.
Sites themselves predate DevDay as shareable web properties built through ChatGPT; the upgrade is what they can now contain. With connected plugins and integrated data, a site can embed working functionality — and the multi-user mechanics are the substantive part: everyone on a team uses the identical app, but each under individual accounts, individual data access, and individual permissions.
Per-user permissions: when a page becomes an app

The permission model is what separates this from publishing. A shared artifact with one owner's credentials baked in is a demo; an artifact where each visitor's access reflects their own identity is software. That distinction is what lets a site built in an afternoon serve as a real internal tool — the sales dashboard shows each rep their own pipeline, the data app touches only what each viewer is entitled to.
This mechanic rides the identity rail OpenAI expanded the same day: Sign in with ChatGPT went global, giving sites and plugins a universal account layer to authenticate against. Identity, app surface, and data access are converging into one platform stack.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
The creator-economy angle
Public profiles give ChatGPT-native creation a discovery layer it lacked: things people build — sites, tools, experiments — get a durable, linkable home attached to their maker. That is the seed of a creator economy inside the 1.2-billion-weekly-user surface, particularly combined with the same day's plugin extension launch and improved plugin discovery, which give more ambitious builders a path from showcased hobby project to distributed product.
OpenAI is visibly assembling the loop platforms need: build (Sites, plugins), identity (profiles, Sign in with ChatGPT), discovery (profiles public, in-conversation plugin recommendations), and distribution (the directory, the sidebar). Profiles are the smallest piece, but they are the one that makes the work visible.
Who should pay attention
Individual builders get the immediate value: a public profile is a portfolio that updates itself as you create. Small teams get an unexpectedly capable internal-tools path — sites with plugins, data, and per-user permissions cover a real slice of what previously required a deployed web app. Workspace admins should note the timing gap: profiles reach individuals before Enterprise controls arrive, so policy on what employees may showcase publicly deserves a look before the feature reaches your users.
For the low-code and internal-tools market, upgraded Sites are a genuine competitive event: the build-a-permissioned-app-by-conversation workflow now lives inside the tool their users already have open.
Enterprise controls and social mechanics: what to watch
Three timelines matter: how gradual the profile rollout proves, when Enterprise support and its governance controls land, and how far Sites' plugin and data integrations extend — each step widens what a conversationally built app can legitimately do. Watch also whether profiles grow social mechanics beyond showcase — following, discovery feeds — which would make ChatGPT a network, not just a tool with pages.
The near-term action is small: builders should claim and curate their profile as it arrives, and teams should try one internal workflow as a permissioned site to see whether the ceiling is high enough for real work.
Developer Action Items
- ☐ Verify the claim on the official OpenAI / ChatGPT page (or OpenAI), not from this recap alone.
- ☐ Name the surface that moved — API, policy, model, hardware, or commercial terms — before you Slack the thread.
- ☐ Assign one owner a day to read the primary material and decide: this-sprint, this-quarter, or noise.
- ☐ Do not change production on day-one coverage. Watch the vendor changelog and one independent write-up first.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
ChatGPT Adds Teams and Shared Tasks With Schedules and Event Triggers
Read →
ChatGPT Joins Slack and Microsoft Teams: Mention It in Any Thread
Read →
ChatGPT Meetings Plugin Captures Calls and Deletes Audio After Use
Read →
Sign In With ChatGPT Extends Plan Usage to Devin, Notion and Vercel
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement