Team and Enterprise plans for ChatGPT, Claude, and Copilot introduced a layer most people don't expect — a separation between the workspace, the seat assignment, and the individual identity. When the wrong seat lands on the wrong identity, every prompt fails. The error rarely says "license problem" — it says "rate limit" or "free tier" or "account not authorized." Here's how to untangle the four most common licensing tangles on each platform.
How team AI licensing actually works
Every team plan introduces three concepts that the consumer plan doesn't have:
- The workspace (sometimes called organization, tenant, or team). The container that owns the subscription and pays the bill.
- The seat. A purchased license slot. Workspaces buy seats; admins assign them to users.
- The identity. The user account (email + password, Google, SSO) that signs in.
The licensing failure mode is always one of these three pieces being mismatched. The fix depends on which mismatch. Reading the error wording carefully tells you which one.
Issue 1: You're signed in, but the workspace doesn't appear
You expected to see your company workspace after signing in. Instead the AI tool drops you into the personal / free view. Always the same root cause: the identity you signed in with isn't a member of the workspace.
Three possibilities:
- The admin invited you at
jane@company.combut you signed in with Google usingjane@company.com— for some platforms, these are still separate identities even when the email is the same. Re-sign-in with the exact method the invite used. - The invite is still pending. Check your inbox (and the spam folder — see the spam fix) for an invite link, click Accept.
- The admin assigned the seat but didn't actually invite you. They need to do both steps.
For ChatGPT Team: chatgpt.com → click your initials → if you see a "Switch workspace" option, the workspace is attached but you're in personal mode. Switch. If not, you haven't been added — ask the admin to invite.
For Claude Team: claude.ai → click your initials → look for "Workspaces." Same logic.
For Copilot (Pro and M365): see the activation guide — the equivalent of "no workspace" is "license not assigned."
Issue 2: You're in two workspaces, the wrong one loads first
You're a contractor or consultant with seats in multiple AI workspaces. The tool picks the wrong one on sign-in and your prompts come back as "free tier limits reached" or "feature not available on this plan."
The fix on each platform:
- ChatGPT Team: initials → Switch workspace. Pick the right one. The selection is sticky per device.
- Claude Team: initials → workspace switcher at the top of the menu. Same.
- Copilot: sign out, sign in with the email matching the license, see Copilot sign-in guide.
If switching workspaces drops you back to personal every time you reload, you're hitting a sign-in identity drift — check the AI tools login guide Fix 2 (cookies).
Issue 3: The seat shows up in the admin console but doesn't work
The admin sees your name in the user list. The seat shows as "active." You still can't use the paid features. Three reasons, in order of likelihood:
- Propagation delay. Most platforms claim instant assignment but in practice take 5–15 minutes to fully provision. Sign out, wait, sign in.
- The seat is "pending" on the user's side. The admin assigned but never invited; or the invite expired (most are 7-day or 14-day). Admin needs to re-send the invite.
- SSO mismatch. The workspace is set up for SSO via Okta/Entra/Google, and the user has a non-SSO account at the same email. The two identities don't merge. Admin needs to either remove the legacy non-SSO account or migrate it.
Issue 4: Conflicting licenses on the same user
You bought Copilot Pro on your personal MSA. Then your employer assigned you Microsoft 365 Copilot too. Now both signed into the same Windows machine, neither one works reliably. This is a real category — especially on Copilot, where the products literally share a brand.
The rule: each identity gets one license, and the identity that's signed into the app at the moment determines which license applies. To untangle:
- Personal use of Copilot at home, on your personal laptop, with your MSA — Copilot Pro applies.
- Work use in Outlook / Word / Excel / Teams on your work laptop, signed in with your work account — M365 Copilot applies.
- You should not need both. If your employer has M365 Copilot for you, cancel your personal Copilot Pro (see cancellation guide) and request a refund of the unused portion.
For ChatGPT, you cannot have both ChatGPT Plus (personal) and ChatGPT Team (workspace) on the same identity. If you join a Team workspace while having a Plus subscription, the Plus seat is paused automatically and prorated.
Issue 5: API key vs. app subscription confusion
One peculiar source of "licensing" complaints: people who have an OpenAI API key with $50 of credits assume that pays for ChatGPT Plus. It does not. The API and the ChatGPT app are billed completely separately at OpenAI. Same identity, two billing relationships, neither covers the other.
The same is true at Anthropic: a Claude Pro subscription does not grant API access; an API key with billing does not enable Claude Pro features.
If you're getting "subscription expired" while you have $200 of API credit, that's why.
Admin console checks that pinpoint who has what
For admins, here's where to verify license assignments are correct:
- ChatGPT Team / Enterprise:
chatgpt.com→ workspace → Workspace settings → Members. Each row shows role and last sign-in. If "Last sign-in" is "Never," the user hasn't accepted yet. - Claude Team / Enterprise:
console.anthropic.com(for the workspace admin) → Settings → Members. Status column shows Active, Invited, or Disabled. - Microsoft 365 Copilot: Microsoft 365 admin center → Billing → Licenses → Microsoft 365 Copilot → see assigned / available. Then Users → Active users → user → Licenses and apps to verify per-user.
- Copilot Pro (consumer): tied to the individual's MSA. There's no admin console — the user manages it at
account.microsoft.com. - Google Gemini Advanced / Workspace: Google Workspace admin console → Apps → Additional Google services → Gemini. License visibility is in user assignments.
The 5-minute licensing audit
When a user reports "Copilot isn't working" or "ChatGPT Team won't load," the admin's first five minutes:
- Confirm the user has been assigned a seat in the admin console.
- Confirm the user's status is "Active," not "Invited" / "Pending."
- Confirm the email on the invite matches the email the user actually signs in with.
- Confirm the user is signing into the correct workspace (not the personal tier).
- For Copilot, run the user through Steps 1–4 of the activation guide.
This catches the four root causes of 90% of "license isn't working" tickets without needing the user to do anything technical.
When to escalate to vendor support
You've checked the user is assigned, active, in the right workspace, signed in with the right identity. The license still won't enable features. Time to file a ticket. Include in the email:
- Workspace ID or tenant ID (visible in the admin console; for Microsoft, it's the tenant GUID in
portal.office.com→ Settings → Org settings). - User principal name (full email).
- Date and time the license was assigned, in UTC.
- Exact error wording from the user's screen.
- What's been ruled out (the four-step audit above).
This is the difference between a 5-day support ticket and a 24-hour one. Vendors triage based on completeness.
Quick reference
- User can sign in but sees free tier → check workspace membership, not the seat.
- User is in two workspaces, wrong one loads → workspace switcher.
- Seat assigned but features still locked → propagation delay, then SSO mismatch.
- Both personal and work AI licenses on one human → keep the work one, cancel the personal one.
- API credits but no app access → separate billing, separate license.
Team AI licensing has more failure modes than consumer billing — but they're all variations on the same root question: which identity, which workspace, which seat. Answer those three and almost any "license problem" resolves itself.