OpenAI rolls out Sign in with ChatGPT for partner apps
OpenAI is testing ChatGPT as an identity option for partner apps, starting with Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel, with separate approval still required for plugin permissions.
OpenAI has begun rolling out Sign in with ChatGPT in beta, turning ChatGPT accounts into a sign-in option for selected partner apps and plugins. The first partner list is narrow, but the change matters because it connects ChatGPT, Codex, plugins, and external SaaS onboarding through a shared identity flow while leaving data permissions as a separate approval step.
Key takeaways
- Sign in with ChatGPT is now in beta for selected plugins and partner sites.
- Initial partners include Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel.
- OpenAI says partners receive identity information only: name, email, and profile picture when available.
- Plugin or app access still requires a separate permission review.
- Enterprise organizations can manage the feature through admin controls and approved-application settings.
What OpenAI changed
OpenAI's new Help Center page describes Sign in with ChatGPT as an identity-provider sign-in option. Users can create, link, or access accounts on supported external applications with their ChatGPT identity where the partner has enabled the flow.
The feature also appears in the ChatGPT and Codex changelog entry dated July 29, 2026. OpenAI says the beta is starting across selected plugins and partner sites, with Airtable, GitLab, HubSpot, Notion, Supabase, and Vercel as the initial group.
That makes this more than a convenience button. It is an early platform move around account linking for ChatGPT-connected work, especially where users jump between ChatGPT, Codex, plugins, and external tools.
The permission boundary
The most important limit is the permission split. OpenAI says signing in shares only identity data with the partner: name, email address, and profile picture if present. It does not independently share ChatGPT conversations, memory, files, tokens, billing information, or other account data.
Any additional access still goes through a separate permission request. For operators, that distinction matters: Sign in with ChatGPT may reduce account setup friction, but it should not be treated as blanket authorization for a connected app to read or write workspace data.
Admin controls to check
OpenAI says Sign in with ChatGPT is available globally to authenticated ChatGPT users, including users in Enterprise organizations, but organization policy can restrict availability. Admins can turn the feature off or require approved applications before members use it.
Teams that already manage plugin access should review this quickly. A sign-in feature can look harmless to users while still changing how accounts are created, linked, and governed across external services.
Why this matters for LinkLoot readers
For individual creators and builders, the immediate benefit is faster onboarding into supported apps. For companies, the practical question is governance: who can use ChatGPT identity, which partner apps are approved, and which separate plugin permissions are acceptable.
The rollout is still beta and partner-limited. The next signal to watch is whether OpenAI expands the partner list, adds more admin reporting, or makes the identity flow a default path inside the ChatGPT plugin directory.
Source check
- OpenAI Help Center confirms the identity flow, initial availability, shared identity fields, separate permissions, and admin controls.
- ChatGPT and Codex changelog lists the July 29, 2026 beta rollout and initial partner apps.
- The New Indian Express independently reports the beta partner rollout and the stated permission boundary.