> **ChatGPT is no longer creating/resolving Business workspace membership for new users.**
This happens through two independent paths:
1. A user receives a valid Business invitation, opens the invitation link, signs in with the exact invited email address, but the Business workspace is never attached to the account.
2. A completely new user under my verified corporate domain successfully verifies the email address, but the Business workspace is still not associated with the account.
Both of these flows worked normally in this same workspace before this regression began.
---
# 1. What worked before
This is important because this is not a workspace that has never been configured correctly.
Previously, in this same ChatGPT Business workspace:
- I could invite a user.
- The user could open the invitation.
- The user could authenticate using the invited email address.
- The Business workspace would appear normally for that user.
The verified corporate-domain flow also worked previously.
A user signing up/logging in using an account from the verified corporate domain could receive the expected Business workspace association according to the configuration available in my Admin/Identity settings.
So this appears to be a **regression in an existing workspace that previously worked**, rather than a new workspace configuration issue.
---
# 2. When the regression started
There is one timeline detail that may be relevant to engineering.
My ChatGPT Business subscription is under a long-term promotional seat arrangement.
The workspace was functioning normally.
I then **added and paid for two additional seats**.
After that change, I began experiencing the membership problem described in this post.
I am **not claiming that purchasing the additional seats caused the bug**.
I am only providing the timing because it may help engineering determine whether the workspace entered an inconsistent membership, billing-baseline, seat-entitlement, or subscription state after the seat change.
Before the regression, users already inside the workspace continued functioning.
The problem affected users who needed to be added afterward.
---
# 3. What happens with a normal invitation
Originally, even after the regression started, I could still create invitations.
This is why the current inability to create invitations must not be confused with the original problem.
The original flow was:
```text
Owner sends Business invitation
↓
Invitation email is successfully received
↓
Recipient opens the new invitation link
↓
Recipient signs in using exactly the invited email
↓
ChatGPT authentication succeeds
↓
Personal ChatGPT account loads
↓
Business workspace never appears
↓
User remains in Personal
The user was not receiving an “incorrect password” error or failing authentication.
The invitation itself existed.
The recipient could follow it.
The failure occurred when the account should actually become associated with the Business workspace.
The workspace simply did not appear in the account/workspace selector.
4. This happened with multiple users and fresh invitation links
I repeated this process multiple times.
I tested:
-
newly generated invitation links;
-
different recipient email addresses;
-
signing completely out before opening the invitation;
-
signing in with exactly the email address that received the invitation;
-
clearing browser state;
-
fresh browser sessions;
-
private/incognito sessions;
-
checking the workspace selector after authentication.
The result remained the same:
The invited user authenticated successfully, but the Business workspace was not attached to the account.
5. Independent reproduction from another city, device and network
I also reproduced the primary problem completely outside my own environment.
This was an important test because OpenAI Support initially suggested browser/session troubleshooting.
I asked another person in a different city to provide a separate email address.
I sent that person a Business workspace invitation.
He then performed the process independently using:
-
his own computer;
-
his own browser;
-
his own ChatGPT session;
-
his own email account;
-
his own internet connection;
-
another network/IP;
-
and another physical location.
He opened the invitation himself and logged in using the exact invited email address.
The result was exactly the same:
Invitation received
↓
Invitation opened
↓
Authentication successful
↓
Personal workspace/account loads
↓
Business workspace is absent
This reproduction is important because it makes a local browser/cache/network explanation extremely unlikely.
The same missing-workspace behavior exists outside my computer, my browser, my cookies, my IP address and my physical location.
6. Current membership situation
Before this regression, I had users successfully using the Business workspace.
During troubleshooting, I removed users so that I could try inviting them again from a completely clean state.
That created another practical problem:
Once I removed a user, I could no longer get that user back into the workspace.
I currently have only two members remaining attached to the workspace:
-
the owner/admin account;
-
one member who joined before this problem started.
I have intentionally not removed that last existing member, because based on every reproduction so far, I have no confidence that I would be able to add that person back afterward.
In other words, troubleshooting by removing existing members has effectively caused me to lose usable workspace membership one user at a time.
7. Independent second path: verified corporate domain
Because the normal invitation path was not producing membership, I tested a completely different route.
I have a corporate domain verified through OpenAI’s identity/admin configuration.
For privacy, I will refer to it publicly as:
[verified corporate domain]
The exact domain and workspace identifiers are available to OpenAI in Support Case #13101564.
The domain was:
-
successfully verified;
-
mapped to the affected ChatGPT Business workspace;
-
configured using the Automatic Account Creation option available in the admin interface.
I also explicitly mapped the verified domain to the affected Business workspace.
Despite this, completely new corporate users were still not associated with the Business workspace.
This is particularly important because it reproduces the underlying membership failure without depending on a normal invitation link.
8. Fresh corporate account test
To eliminate stale state from an existing user account, I created a completely new email account under the verified corporate domain.
I will call it:
[fresh corporate test user]
The exact address is available privately in Support Case #13101564.
During OpenAI signup/authentication, the HAR shows that OpenAI successfully recognized and verified the email address.
The authentication state included:
email_verification_mode = onboarding
email_verified = true
So email verification itself was successful.
The user then completed authentication and entered ChatGPT.
At this point, I would expect the configured domain/workspace relationship to be resolved.
Instead, ChatGPT returned this account state:
claimed_domain_org_id = null
email_domain_type = unknown
groups = []
tenants = []
The only organization present for the new user was the user’s Personal organization.
There was no Business tenant/workspace association.
9. /me HAR evidence
The relevant normal ChatGPT request was:
GET /backend-api/me
The response for the newly created and email-verified corporate user contained state equivalent to:
{
"email": "[fresh user at verified corporate domain]",
"claimed_domain_org_id": null,
"email_domain_type": "unknown",
"groups": [],
"tenants": []
}
OpenAI Request ID
3d397094-2493-4969-afde-b3b90879f816
Approximate timestamp
2026-08-13 22:06:29 UTC
This appears highly relevant.
The authentication system had already confirmed that the user’s email was verified.
The email uses the corporate domain that was verified and mapped in the admin configuration.
Yet the ChatGPT account state still reports:
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
I am not claiming to know the exact internal meaning of these fields.
However, their combination is consistent with what I observe in the UI:
ChatGPT is not resolving the user into the Business workspace.
10. Account resolver confirms Personal/Free only
The same fresh corporate-user HAR also contains the normal ChatGPT account-resolution request.
The account state showed:
structure = personal
workspace_type = null
plan_type = free
and the account ordering contained only the newly created Personal account.
The expected Business workspace was absent.
So there are two independent normal ChatGPT responses showing the same state.
/me
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
Account resolution
structure = personal
workspace_type = null
plan_type = free
Business workspace = absent
This is not merely a workspace-switcher rendering problem.
The backend account state itself does not contain the Business workspace for the new corporate user.
11. ChatGPT’s own domain backfill reports success but does not change the result
During this normal browser flow, ChatGPT itself called:
POST /backend-api/accounts/backfill_workspace_owner_domains
This was part of the normal captured browser traffic.
The backend returned:
HTTP 200
and:
{
"success": true
}
OpenAI Request ID
93eb6f01-9318-4c01-b2f1-9a9a5ff935b9
Approximate timestamp
2026-08-13 22:06:32 UTC
However, no Business workspace association was created.
The user still remained:
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
structure = personal
plan_type = free
This seems like a particularly useful server-side trace for engineering.
The operation reports success, while the effective user/workspace state remains unchanged.
12. The domain configuration was rebuilt from scratch
I also tested whether this was caused by stale domain configuration.
I completely removed/unlinked the verified corporate domain.
Then I:
-
added the corporate domain again;
-
completed verification again;
-
mapped it back to the Business workspace;
-
confirmed the Automatic Account Creation configuration;
-
created another completely new corporate user;
-
completed signup and email verification again;
-
logged into ChatGPT with that new user.
The same problem remained.
The new user was again created/resolved only as Personal/Free and did not receive the Business workspace association.
Therefore simply deleting, re-verifying and re-mapping the domain did not repair the state.
13. This strongly suggests one common membership-resolution failure
The reason I believe the invitation issue and verified-domain issue are connected is that they are two different entry paths that appear to fail at the same final stage.
Invitation path
Valid Business workspace
↓
Invitation is created
↓
Recipient receives invitation
↓
Recipient opens invitation
↓
Recipient authenticates successfully
↓
Business membership should appear
↓
IT DOES NOT
↓
User remains Personal
Verified-domain path
Corporate domain verified
↓
Domain mapped to Business workspace
↓
Automatic Account Creation configured
↓
Completely new corporate user
↓
Email successfully verified
↓
ChatGPT loads
↓
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
↓
Business workspace absent
↓
User remains Personal/Free
The common failure is:
Creation/resolution of Business workspace membership.
That is the issue I most urgently need OpenAI to investigate.
14. This is a regression, not expected behavior for this workspace
Another reason this is important:
Both mechanisms worked before.
Before the regression:
Invitation → user joined successfully
and the verified-domain behavior also successfully associated users with the Business workspace.
After the regression:
Invitation → user authenticates → no Business workspace
and:
Verified-domain user → email verified → no Business workspace
Something changed in the effective backend state of this existing workspace.
15. Possible correlation with the seat change
Again, I do not want to overstate this as the root cause.
But the timing may be useful.
The problem began after I added and paid for two additional Business seats.
The workspace had been functioning before that change.
My billing arrangement had effectively been expanded, but today only two existing members remain attached to the workspace because users removed during troubleshooting could not be added back.
A current backend seat request reports:
{
"seat_type_counts": {
"default": 2,
"usage_based": 0,
"automation": 0,
"prolite": 0
},
"maximum_seats": 1000
}
So the normal seat endpoint does not indicate that the workspace has reached a hard capacity limit.
I would appreciate engineering checking whether the seat purchase/change left any stale or inconsistent state across:
-
billed seat baseline;
-
active seat entitlement;
-
Business membership;
-
workspace account state;
-
subscription entitlement;
-
or membership indexes.
Again, this is a correlation based on when the regression began, not a claimed root cause.
16. OpenAI Support Case #13101564
I already opened an official OpenAI Support case:
Case #13101564
The first Support response acknowledged that an invited user could not join the Business workspace despite an available seat and an invitation having been sent.
Support asked me to:
-
remove/cancel the pending invitation;
-
clear browser cache and cookies;
-
completely restart the browser;
-
alternatively use an Incognito/Private window;
-
generate a completely new invitation;
-
use the exact email address that received the invitation;
-
use the newly generated invitation link rather than an older link;
-
check the workspace selector after acceptance.
I completed those troubleshooting steps.
I have now also gone substantially beyond them.
The problem has been reproduced:
-
with newly generated invitations;
-
with multiple email accounts;
-
after clearing browser state;
-
in private/incognito sessions;
-
with completely fresh corporate accounts;
-
after rebuilding the domain configuration;
-
and independently by another person in another city, on another computer and another network.
At this point I believe repeating browser/cache troubleshooting will not address the underlying problem.
17. NEW secondary issue: now new invitations themselves also fail
There is now an additional problem.
I want to keep this separate because it appeared later and is not the original issue described above.
After repeatedly removing/recreating invitations while troubleshooting the original membership failure, new invitations eventually stopped being created successfully.
The current workspace state before one of these attempts showed:
current default seats = 2
maximum_seats = 1000
and the pending invitation list had been cleared.
A normal invitation request then reached the ChatGPT backend:
POST /backend-api/accounts/[workspace]/invites
and returned:
HTTP 200
but the application response contained:
{
"account_invites": [],
"errored_emails": [
{
"email_address": "[redacted recipient]",
"error": "Unable to invite user due to an error."
}
]
}
Request ID
5727044d-d2ec-4bc1-94d5-2232f8d8d0c9
Approximate timestamp
2026-08-13 22:14:40 UTC
An earlier invitation creation attempt also returned the same application-level failure:
924c5b5b-b608-422a-b42c-8e7b60f13953
This is now another issue that needs repair.
But I want to emphasize again:
This later invitation-creation error does not explain the original problem.
When invitations were still being created successfully, recipients already could not obtain the Business workspace.
And the verified-domain flow continues to reproduce the original membership problem independently of invitation creation.
18. Why this does not look like a local client problem
Across the normal product flows and HAR captures:
-
authentication succeeds;
-
the corporate email is verified successfully;
-
the paid Business workspace remains active;
-
existing members can still use the workspace;
-
admin APIs are accessible to the owner;
-
the corporate domain is verified;
-
the domain is mapped;
-
Automatic Account Creation is configured;
-
the issue survives a complete domain reset;
-
fresh corporate users still receive only Personal/Free state;
-
/mereports no tenant/domain association; -
account resolution contains no Business workspace;
-
ChatGPT’s domain backfill returns HTTP 200 /
success:true; -
the invitation-acceptance problem reproduces on another person’s device/network/location.
These facts together strongly suggest a server-side account/workspace state inconsistency rather than a problem limited to my browser or network.
19. Operational impact
This is currently blocking my operation.
I pay for ChatGPT Business because I need to use it as a multi-user workspace.
I cannot safely remove the last existing pre-regression member because I have no confidence I could add that person back afterward.
Users that I need to add cannot get into the workspace.
The alternative verified-domain path also does not create the Business membership.
And now, as a secondary issue, creating new invitations itself is also failing.
My next billing date is August 24, 2026.
I am extremely concerned about reaching another billing cycle while the core Business workspace membership functionality remains unusable for my operation.
I have already spent substantial time reproducing this across accounts, browsers, devices, networks and domain configurations.
I urgently need this moved to a team that can inspect and repair the server-side workspace state.
20. What I am asking OpenAI engineering to investigate
If an OpenAI staff member sees this post, please help escalate Support Case #13101564 to the team responsible for ChatGPT Business workspace membership / account identity / verified-domain association.
The most important questions are:
-
Why can a valid invited user authenticate successfully but never receive the Business workspace membership?
-
Why does a brand-new user under the verified and mapped corporate domain return:
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
- Why does the account resolver contain only:
structure = personal
plan_type = free
with the Business workspace absent?
- Why does:
POST /backend-api/accounts/backfill_workspace_owner_domains
return:
{"success": true}
without producing any observable domain/workspace association?
-
Is the verified-domain mapping present in the identity/admin system but missing, stale or inconsistent in the ChatGPT Business membership service?
-
Did the seat/billing change leave the workspace in a stale or inconsistent membership/entitlement state?
-
Are there stale membership indexes, tenant assignments, account mappings or workspace-entitlement records that need to be rebuilt/reindexed?
-
Why did a workspace that previously allowed successful invitation acceptance and verified-domain association stop creating new memberships?
-
As a secondary problem, why does the invitation creation service now return HTTP 200 but create zero
account_invites?
Most importantly:
Please repair the workspace state so that Business membership can be created/resolved again.
The priority is restoring:
invited user
↓
accepts invitation
↓
Business workspace appears
and restoring the previously working verified-domain behavior for new users.
The newer invitation-creation failure should also be repaired, but it is secondary to the original membership problem.
21. Most relevant OpenAI Request IDs
PRIMARY — Fresh verified-domain user’s /me state
3d397094-2493-4969-afde-b3b90879f816
Approximate time:
2026-08-13 22:06:29 UTC
Observed state:
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
PRIMARY — Account resolver for the fresh corporate user
d72942dd-7919-4f44-bb26-582e08a501de
Observed state:
structure = personal
workspace_type = null
plan_type = free
Business workspace absent
PRIMARY — Domain backfill
93eb6f01-9318-4c01-b2f1-9a9a5ff935b9
Approximate time:
2026-08-13 22:06:32 UTC
Result:
{"success": true}
but no Business membership/domain association appeared.
SECONDARY — Current invitation creation failure
5727044d-d2ec-4bc1-94d5-2232f8d8d0c9
Approximate time:
2026-08-13 22:14:40 UTC
Result:
HTTP 200
account_invites = []
"Unable to invite user due to an error."
SECONDARY — Earlier same invitation-creation failure
924c5b5b-b608-422a-b42c-8e7b60f13953
Same application-level invitation error.
22. HAR files and privacy
I have multiple HAR captures showing the normal browser flows described above.
They include:
-
fresh verified-domain account signup/authentication;
-
successful email verification;
-
/backend-api/me; -
ChatGPT account resolution;
-
the domain backfill response;
-
workspace seat state;
-
invitation state;
-
and the newer invitation-creation failure.
I am intentionally not publishing raw HAR files in this public community post, because HAR captures can contain authentication/session information.
I can provide sanitized captures, screenshots, exact account/workspace identifiers and additional Request IDs privately through OpenAI Support Case #13101564.
Final summary
This is the key point I hope reaches OpenAI engineering:
The original problem is not “an invitation email cannot be sent.”
The original problem is:
ChatGPT Business workspace membership stopped being created/resolved for new users in a workspace where this functionality previously worked normally.
It fails when the user enters through a valid invitation.
It also fails independently for completely new, successfully email-verified users under the verified corporate domain.
The HAR shows the corporate user authenticated successfully but still resolves to:
claimed_domain_org_id = null
email_domain_type = unknown
tenants = []
Personal / Free only
even though ChatGPT’s own domain backfill reports:
{"success": true}
A separate person reproduced the invitation membership failure from another city, another computer and another network.
Only after extensive troubleshooting did the second issue appear, where new invitations themselves now fail to be created.
Please help escalate Case #13101564 for an internal ChatGPT Business workspace membership/state investigation.
My operation is currently blocked and my next billing cycle is approaching.
Thank you.