ChatGPT sign-in is showing up in your business tools

A new login button, Sign in with ChatGPT, now sits on six tools a lot of small businesses run day to day: HubSpot, Notion, Airtable, GitLab, Supabase, and Vercel.

OpenAI opened the feature in beta on Supabase on July 29, 2026. By late August it had rolled out to HubSpot, Notion, Airtable, GitLab, and Vercel as well. The pitch is fewer steps to connect an account: pick ChatGPT, approve, and you are signed into the partner site, with your name, email, and profile picture shared automatically.

How ChatGPT sign-in works

The flow is standard OAuth with one twist. Someone clicks Sign in with ChatGPT on the partner site, or connects the partner as a plugin from inside ChatGPT, and approves the request. If the email on their ChatGPT account matches an existing account on the partner site, the two get linked. If it does not, or if they never had an account there, a new one gets created on the spot. Granting a plugin access to read or write data is a separate approval from the sign-in itself, so a person can be logged in without the plugin having touched their data, or the other way around.

The account sprawl problem for a small team

Most small businesses that use HubSpot, Notion, or Airtable route logins through Google Workspace or Microsoft 365 single sign-on, so every account ties back to one directory the owner controls. ChatGPT sign-in opens a second door. An employee's personal ChatGPT account, tied to a personal email, can now create or link an account on a work tool without touching that directory at all. The account exists. The admin console may never show how it got there.

• What gets shared automatically on sign-in: name, email address, profile picture
• What does not get shared automatically: read or write access to your data in that tool
• What is not yet consistent across partners: whether an admin can turn the login option off

What to check this week

1. 1

   Check admin settings

   Log into HubSpot, Notion, Airtable, GitLab, Supabase, or Vercel as an admin and look for a setting that restricts login to your enforced SSO. Not every tool exposes this yet, so ask your account rep if you cannot find it.

2. 2

   Add it to your offboarding checklist

   An account created through ChatGPT sign-in with a personal email will not show up in a Google Workspace or Microsoft 365 audit. When someone leaves, search each tool's user list by name, not just by company domain.

3. 3

   Set a one-line policy

   Tell the team whether signing into work tools with a personal ChatGPT account is allowed. One sentence in your AI policy closes the gap before someone opens it by accident.

If your team already lives in HubSpot, Notion, or Airtable, this is a small config check, not a rebuild. Bring me your login setup and I will tell you where the gap actually sits.