Issue with workspace seat types getting changed by the system

I’m not sure if this is the right place to post, or if anyone else has run into the same issue.

Our workspace just renewed the Business ChatGPT & Codex plan this April.

In June, we bought some Codex credits. After that, I adjusted the workspace settings under “Monthly usage limits” → “Per user override” so that only 2 members have a quota to use Codex credits, while setting the quota for all other members to 0. I didn’t set any of the member seat types.

But the next day, I found out that everyone’s seat type had been changed to Codex. Now, changing it back to the original ChatGPT seat type requires us to pay again. Which of my actions could have caused this?

We even have one member whose account is still disabled. After the last automated moderation error blocked us, everyone else got unlocked successfully, but that specific member is still blocked.

We already submitted a case, but we know it’s going to take some time to get a reply.

Hi @Eric3345678 — thanks for flagging this. That doesn't sound like expected behavior.

Changing Monthly usage limits → Per user override to control Codex credit usage should not normally switch everyone's seat type to Codex, so this may require further investigation by the Support team.

I also noted the member who remains blocked after the previous moderation-related issue, and that should be reviewed as well.

Could you share your case ID? We can help monitor the ticket and ensure both the seat-type changes and the still-disabled account are included in the investigation.

-Mark G.

Hello Mark ,

Workspace Seat Type - Case Number: 09882790

Account Issue - Case Number: 09783814

This issue has been bugging us for days. Really appreciate your help with this.

Thanks for your help.

We are experiencing the same issue. Please help with the following case number.
Case Number: 09885652

We are experiencing what appears to be the same or a highly similar issue in our ChatGPT Business workspace.

Our paid annual Business workspace has been unable to access ChatGPT since Wednesday morning Japan time. Many users are now shown as Codex-only seats and cannot use ChatGPT.

In our case, we have an annual ChatGPT Business subscription with 180 seats already paid for.

We have a previous Billing screenshot from June 2, 2026 showing:

  • Business plan, annual

  • Current cycle: March 16, 2026 – March 16, 2027

  • ChatGPT seats: 170 / 180 in use

  • Codex seats: 0 in use

The current Billing page now shows:

  • Codex seats: 170 in use

  • Standard ChatGPT seats are no longer shown as before

  • Changing users back to Standard ChatGPT seats leads to a billing / purchase screen

We did not request this change, and we are not trying to purchase new seats. We need our already-paid Standard ChatGPT Business seats restored.

We have contacted OpenAI Support multiple times through the official support chat and by email. The support chat initially said the issue was escalated to a support specialist, but we still have no case / ticket number, no ETA, and no clear response from a human specialist.

We are intentionally not approving pending “seat type update” requests because we are concerned that doing so may trigger unintended new purchases or duplicate billing.

This looks like a Business workspace seat mapping / billing / provisioning issue related to Codex seats, not a normal seat purchase issue.

@OpenAI_Support, could you please confirm whether this is being investigated as a broader seat mapping / provisioning bug, and advise how affected Business customers should proceed without triggering duplicate billing?

Thanks everyone for reporting this and sharing the details. I can see a few of you are running into the same issue with your seat type being changed unexpectedly.

Our internal team is currently investigating, and they're actively working on it. I don't have any additional details to share just yet, but I'll post an update here as soon as we hear back from them.

If anyone notices any new behavior or changes in the meantime, feel free to add them to this thread.

-Mark G.

Please let us know for updates, as the use of Chatgpt is essential for our work processes.

Thank you for responding to our current situation regarding the sudden seat change.

Thanks for following up @Okabegallery, and I completely understand the urgency given how important ChatGPT is to your team’s workflow.

I’ll be posting updates in this thread as soon as we receive more information from the team investigating the issue. For now, there isn’t anything new to share, but we’ll keep everyone informed here when we have an update.

Appreciate your patience while this is being looked into.

-Mark G.

Hi Mark,

Thank you for the update.

Our workspace is still affected as of Monday morning Japan time, and ChatGPT access has not been restored since Wednesday morning Japan time.

What is especially concerning is that we still do not have a case / ticket number, even though we have contacted OpenAI Support many times through the official support chat and also by email.

The support chat initially said that the issue was escalated to a support specialist, but we have not received:

  • a case / ticket number

  • confirmation that a human specialist has reviewed our workspace

  • confirmation that our workspace is included in the internal investigation

  • an ETA for restoration

  • written guidance on whether to keep pending “seat type update” requests unapproved

Our situation remains the same:

  • We already paid for 180 ChatGPT Business seats on an annual plan.

  • Our June 2 Billing screenshot shows ChatGPT seats: 170 / 180 in use and Codex seats: 0.

  • The current Billing page shows Codex seats: 170 in use.

  • Users cannot access ChatGPT.

  • Changing users back to Standard ChatGPT seats leads to a billing / purchase screen.

  • We are intentionally not approving pending seat type update requests because we are concerned about duplicate billing or unintended new purchases.

Could you please help ensure that our workspace is actually included in the internal investigation, and advise how we can privately provide workspace details if needed?

Also, could OpenAI please provide affected Business customers with a case / ticket number or another way to confirm that each affected workspace is being tracked?

This has now become a serious business continuity issue for us.

Do you have a complaint email address? There is a case number that you can include in this room.

Thanks, @Okabegallery.

We have already contacted OpenAI through the official Help Center support chat many times, and we also sent emails to support@openai.com.

However, we still have not received any case / ticket number. This is one of the most concerning parts of our situation.

The support chat initially said the issue was escalated to a support specialist, but as of now we still do not have:

  • a case / ticket number

  • confirmation that a human specialist has reviewed our workspace

  • confirmation that our workspace is included in the internal investigation

  • an ETA for restoration

  • guidance on whether pending “seat type update” requests should remain unapproved

We do not want to share private workspace details publicly. If OpenAI Support needs our workspace details, we can provide them privately through the official support channel.

@OpenAI_Support / Mark, could you please advise how affected Business customers without a case number can make sure their workspace is being tracked?

Do you have a case number like this email screenshot? That would make it easier for @OpenAi _Support Mark to check the issue.

Thank you, @Okabegallery. That is very helpful.

Unfortunately, we still do not have a case number like yours.

We have contacted OpenAI Support many times through the official support chat, and we have also sent emails to support@openai.com. The support chat initially said that the issue was escalated to a support specialist, but we have not received any case / ticket number yet.

Our workspace is still affected:

  • Paid annual ChatGPT Business subscription with 180 seats

  • June 2 Billing screenshot: ChatGPT seats 170 / 180, Codex seats 0

  • Current Billing page: Codex seats 170

  • Users still cannot access ChatGPT

  • Changing users back to Standard ChatGPT seats leads to a purchase screen

  • Pending seat type update requests are still being left unapproved to avoid duplicate billing

We are very concerned that our workspace may not be properly tracked in the support system because we have no case number.

@OpenAI_Support / Mark, could you please advise how affected Business customers without a case number can make sure their workspace is included in the internal investigation?

We are also experiencing this issue.

On Monday, June 8, our ChatGPT seats were changed to Codex seats, making them unusable unless we add credits. Over the past few days, we have been contacting support through the official Help Center support chat, and we have only been contacted once, under Case Number: 09930547, asking whether we wanted to increase or reduce the number of seats…

After replying to that message on Thursday, June 11, explaining the issue again and providing the latest invoice paid in March, screenshots of the Billing panel, the Organization ID, the Workspace ID, and other supporting information through the appropriate support channel, we still have not received any response by email or through the support chat.

We manage several companies, each with its own Workspace and separate plan billed to the corresponding company. In another one of them, we have experienced the same issue, also since Monday, June 8. In that case, despite following the same procedure, we have not received any communication, we do not have a Case Number, and it seems that emails or communications through the official Help Center support chat are not progressing, as today marks 7 days without a response, even though we were told from the first day that the case was being escalated to a specialized agent.

As you can understand, this is a serious issue affecting the daily work routine of the departments impacted in both companies.

We would appreciate any help on this matter.

Hi @OpenAI_Support / Mark,

I would like to follow up regarding

Workspace Seat Type - Case Number: 09882790

Account Issue - Case Number: 09783814

and ask whether there have been any updates or progress on this matter.

This issue has been pending for some time, and we would greatly appreciate any information you can provide regarding its current status or the expected timeline for resolution.

Best regards,

Hai Mark,

We haven’t received any updates on this issue yet. Please help us resolve this issue quickly, as our company relies on this chatbot.

Case Number: 09885652

The company’s communication plan data is currently in the chat history. Please expedite the resolution of this issue.

@OpenAI_Support We have also had this problem since June 5th - our business account (98 seats chatgpt) was incorrectly banned/disabled by OpenAI; OpenAI reached back out and said it was in error, but then all of our users were marked as Codex-only seats and not ChatGPT (and blocked from access).

we were fully paid for June 2 - July 2.

I manually flipped them all back to ChatGPT, but a couple of days later, they are reverted again to Codex only, and I cannot switch them back to ChatGPT now without having to pay or add seats!

We are now dead in the water and this is blocking our tool use and our business!

our case is 09912118

please help!

Update: I found that our support email did include a case number.

Our case number is 09923628.

However, the issue is still unresolved, and we have not yet received confirmation that our workspace is included in the internal investigation or that a human Billing / Provisioning / Workspace Operations specialist is handling it.

@OpenAI_Support Hai Mark G,

Is there any update on this issue? It’s been a while since we’ve had this issue?

@OpenAI_Support
Case Number: 09924416

the issue is still unresolved, and we have not yet received confirmation that our workspace is included in the internal investigation or that a human Billing / Provisioning / Workspace Operations specialist is handling it.