Fastest fix: the seat almost always fails because the email the user logs in with is not the exact email that was invited (an alias like john+gpt@ or a different domain counts as a different person). Have the admin open Workspace settings -> Members, revoke the old invite, and re-invite the user’s current login address verbatim, then have the user click within a few minutes. If the emails already match, the next suspects are a past-due payment (every seat pauses) and SSO enforcement (the workspace only appears when you enter through your company’s SSO portal).
One naming note up front: OpenAI renamed “ChatGPT Team” to “ChatGPT Business” on 29 Aug 2025, and existing Team workspaces were migrated automatically. The admin console, the upgrade dropdown, and the subscription label now say Business. The activation flow and every fix below are identical; if you still see the word “Team” somewhere, it is just a stale screenshot or an old browser tab.
The activation chain is: admin invites email X at chatgpt.com/admin -> X gets the email -> clicks the Join link -> logs in or signs up -> the workspace appears in the account-switcher dropdown -> the user switches into it to use the seat. Anything stuck mid-chain reads as “invite sent but seat not active.”
Which bucket are you in?
| Symptom the user/admin sees | Most likely cause | Jump to |
|---|---|---|
Admin Members list shows Pending / Invited; user swears they accepted | Login email is an alias/variant of the invited email | Cause 1 |
User clicks the link and sees link no longer valid / expired | Invite expired (7 days) or was already opened once | Cause 2 |
Red Past due banner in admin billing; all seats stopped working | Monthly card charge failed | Cause 3 |
| User logs in fine but the workspace never shows in the dropdown | SSO is required; user logged in with email + password | Cause 4 |
After clicking, the URL lands on a Personal workspace | Invite was accepted on the wrong (personal) account | Cause 5 |
Common causes
Cause 1: Login email is not an exact match
OpenAI matches invite emails case-insensitively but treats aliases and dots as distinct identities. An invite sent to john@company.com does not match a login of john+gpt@company.com or John.Doe@company.com (Gmail collapses the dot and the plus-tag; OpenAI’s account system does not). To OpenAI these are two different people, so the seat is “waiting” on an account that never accepts it.
How to judge: the admin’s Members list shows the user as Pending (or Invited), yet the user has the email and insists they clicked. Have the user open chatgpt.com/account and read their login email back character by character.
Cause 2: Invite link expired or already used
Each Join link expires after 7 days and is single-use. A second open shows link no longer valid. Common triggers: the invite sat for a week before anyone clicked it, or a mobile mail app previewed the link (which can consume the one-time token) before the user clicked it on desktop.
How to judge: the user sees expired or invalid on click, and the admin’s Members list still shows Pending, not Active.
Cause 3: Payment failed / Past due
If the monthly card charge fails (expired card, insufficient funds, a 3-D Secure decline), OpenAI’s billing flips the whole workspace to Past due. Every seat is paused, including a brand-new invite, until the charge clears. As of June 2026 ChatGPT Business is $25/seat/month billed monthly or $20/seat/month billed annually, so a single declined card can stall an entire team.
How to judge: the admin opens chatgpt.com/admin/billing and sees a red banner at the top: Payment failed / Past due / Subscription requires attention.
Cause 4: SSO is enforced but the user logged in without it
ChatGPT Business and Enterprise let an admin turn on Require SSO for the workspace. Once it is on, members must sign in through the configured identity provider (Okta, Microsoft Entra ID / Azure AD, Google Workspace). A plain email-plus-password login at chatgpt.com still lets the user into their Personal account, but the Business workspace stays hidden because that session was never authenticated through SSO.
How to judge: the admin opens chatgpt.com/admin/identity (the Identity & provisioning tab) and checks whether SSO is set to required.
Cause 5: Invite was accepted on the wrong account
Say john@company.com once created a personal ChatGPT account under john@gmail.com. The invite goes to the company email, but when John clicks the link his browser is already signed into the personal gmail.com account, so ChatGPT “accepts” the invite onto that personal identity instead. The seat is consumed by an account that is not the one the admin meant to add.
How to judge: right after clicking, the user’s URL lands on chatgpt.com showing a Personal workspace, not the Business one.
Shortest path to fix
Step 1: Reconcile the emails on both sides
Admin: chatgpt.com/admin -> Members -> find the user -> copy the INVITED email
User: chatgpt.com/account -> copy the LOGIN emailPaste both into a plain-text editor and compare them character by character:
Invited: john@company.com
Logged: John@company.com <- case differs but still matches; unify to lowercase anyway
Invited: jane@company.com
Logged: jane+work@company.com <- alias differs; OpenAI treats this as a separate identity -> WILL NOT matchMismatch -> Step 2. Exact match -> Step 3.
Step 2: Admin re-invites the exact email
chatgpt.com/admin -> Members -> find the old invite -> Revoke
-> Invite members -> paste the user's CURRENT login email verbatim
-> have the user click the Join link within a few minutes (don't let it sit and expire again)Click tips:
- Click in a desktop browser, not inside an email-app preview pane (a preview can silently consume the one-time token).
- Before clicking, confirm the browser is signed into that user’s ChatGPT account: open
chatgpt.comand check the email at the top-right account menu.
Step 3: Admin checks billing status
chatgpt.com/admin/billing ->
top banner reads "Payment failed" / "Past due" / "Subscription requires attention"?
-> Yes = workspace paused, every seat is waiting on payment
-> Update payment method, then retry this period's charge
-> No = jump to Step 4After a successful retry, entitlement can take roughly 10-30 minutes to flow back to the seats. If a seat is still missing past that, the user should sign out and back in to refresh the session.
Step 4: Check SSO enforcement
Admin: chatgpt.com/admin/identity -> Identity & provisioning
-> SSO required (and/or SCIM provisioning on)?
-> If required, users MUST enter through the SSO portal (Okta tile / Microsoft MyApps / Google Workspace app)
-> A direct chatgpt.com email-and-password login will NOT show the Business workspaceThen have the user:
1. Close every chatgpt.com tab
2. From the company SSO portal (e.g. myapps.microsoft.com or Okta), find the ChatGPT app -> click it
3. Complete the SSO flow -> the session should land directly in the Business workspaceIf SCIM (directory sync) is on, membership is driven by your IdP group, not by manual invites; add the user to the mapped group in Okta/Entra and let it sync rather than inviting by hand.
Step 5: Resolve “invite went to the wrong account”
If the user accepted on a personal account:
1. User: top-right avatar -> Sign out of the current personal account
2. Admin: revoke the old invite -> resend
3. User: FIRST sign up / sign in to ChatGPT with the COMPANY email -> THEN open the invite link
4. The invite now binds to the company-email account, not the personal oneStep 6: Confirm the seat is active
User side:
1. Top-right avatar -> the dropdown now lists the company workspace name
2. Switch into it
3. The header shows the workspace name instead of "Personal"
4. The model picker exposes the full Business model set (GPT-5.5, Thinking/Pro modes)
5. Settings -> Subscription reads "Business", not "Free"Admin side:
chatgpt.com/admin -> Members -> the user's status flips from "Pending"/"Invited" to "Active"
chatgpt.com/admin/billing -> "Seats used" increments by 1FAQ
The user clicked “Accept” but the admin still shows “Pending” - why?
Almost always an email-identity mismatch (Cause 1). The user accepted onto a slightly different address (an alias, a +tag, a dot variant, or a personal account). Revoke and re-invite the exact address shown at chatgpt.com/account.
My admin panel says “Business,” but the invite email / our internal docs say “Team.” Are these the same thing? Yes. OpenAI renamed ChatGPT Team to ChatGPT Business on 29 Aug 2025 and migrated existing workspaces automatically. There is no separate “Team” product anymore; any lingering “Team” wording is just an old screenshot or a cached page.
How long is the invite link valid, and can I reuse it?
Seven days, single-use. After that it shows link no longer valid and the admin must resend it from Members (the pending invite row). Don’t forward the link to a third person - whoever opens it first consumes it.
One person’s seat is fine but a coworker’s just stopped working overnight. What changed?
Check chatgpt.com/admin/billing for a Past due banner first (Cause 3) - a failed monthly charge pauses every seat at once. If billing is healthy, check whether SSO/SCIM was turned on or a directory group changed (Cause 4).
The user is in the workspace but only sees GPT-5.5 with no advanced modes - is the seat half-activated? No. A workspace member can see the seat is active (the workspace name appears, Subscription reads “Business”) yet still hit normal Business usage limits or a model picker without the heaviest modes. That is a capability/limit question, not an activation failure - the seat itself is allocated.
Prevention
- Before sending an invite, the admin and the invitee confirm the exact email spelling in Slack or email. Don’t guess.
- Standardize on one corporate domain (e.g.
@company.com); don’t mix in personal Gmail addresses. - Have the user register at
chatgpt.comwith the company email first, then open the invite - this avoids landing the seat on a personal account. - The admin checks
chatgpt.com/admin/billingat the start of each month and replaces soon-to-expire cards proactively, so a single decline doesn’t suspend the whole workspace. - If you run SSO, give new hires a one-line instruction: “Enter through the SSO portal; do not open chatgpt.com directly.” If you run SCIM, add them to the mapped IdP group instead of inviting by hand.
Related reading
- Mobile and web login mismatch
- Subscription not recognized
- Wrong auth method after signup
- Account switch not working
- Verification email missing
Tags: #ChatGPT #Troubleshooting