ChatGPT Business owners are asking for a way to limit who can invite members
A forum post says any member of a ChatGPT Business workspace can invite others and owners cannot switch that off. That matters to anyone managing a team's seats.
The short version
- The post is a feature request. It says ChatGPT Business owners cannot currently stop regular members from inviting people.
- It says OpenAI's documentation acknowledges this limitation.
- The author asks for a setting called "Who can invite new members?" with two choices: owners and admins only, or all members.
- The author wants the rule enforced on the server side, not just by hiding the invite button.
- The post cites Anthropic's Team and Enterprise plans as already offering a comparable switch.
Why it matters
Anyone who pays for team seats expects to decide who fills them. If members can invite freely, an owner can end up policing the membership list by hand. The post shows how a small permission gap turns into ongoing admin work and some distrust inside a team.
What the post actually says
A post on community.openai.com asks OpenAI to give ChatGPT Business workspace owners a way to limit invitations to owners and admins. Our earlier mention read this as a control that had already shipped. The post itself describes a request, and it says the opposite: today, regular members can invite more people and owners have no option to turn that off.
The author also says OpenAI's own documentation openly acknowledges the limitation. We have not seen that documentation ourselves, so treat the claim as the poster's account. Neither a price nor a release date appears in the post.
The scenario that prompted it
The author describes a workspace with five unused, prepaid seats held back for future hires or specific colleagues. A few days later, the owner finds unfamiliar accounts sitting in those seats. The owner removes them, and a day or two later more accounts show up.
When the owner asks who sent the invitations, existing members say they know nothing about it. The owner has no clear invitation history to check, so the source stays hidden. The post calls the result a loop of surprise memberships, manual removals, awkward questions and constant monitoring.
Removing the accounts does not fix anything while every member can still invite someone new.
Control, not just cost
The author is careful on one point: there may be money involved, but they have not verified any extra charges and do not claim every invitation creates one. The argument rests on control. Owners are responsible for deciding who belongs in the workspace and how paid seats are handed out, yet they cannot enforce a rule that keeps those decisions with owners and admins.
The post lists the practical fallout:
- Seats set aside for approved colleagues can be taken by people nobody approved.
- Owners must keep checking and correcting the member list.
- Without a record of who invited whom, nobody is accountable.
- Unexplained additions can erode trust on the team.
The author sums up the idea in one line: "An unused seat represents available capacity." In other words, an empty seat is not approval for just anyone to take it.
What the author wants built
The proposal is a workspace setting titled "Who can invite new members?" with two choices: owners and admins only, or all members. The author stresses that the restriction should be enforced on the server, meaning the system itself would refuse the action. Simply hiding the invite button would not count, because a hidden button is not a real rule.
The author also asks for an invitation history showing who sent each invite, the invited email address, when it was sent and its current status. The post presents this as a supporting feature. It would help with accountability, but it should not replace the ability to block unauthorized invitations in the first place.
Behind both requests is a simple principle. Being allowed to use a workspace and being allowed to grow its membership are two separate responsibilities, and an owner should choose whether to hand over both.
The Anthropic comparison
The post points to Anthropic's documentation for its Team and Enterprise plans. According to the author, those plans include an administrative setting that turns member-to-member invitations on or off. When it is off, only administrators can invite people.
We have not checked that documentation either, so this comparison is the poster's description. The author's point is that team customers can already choose how membership is managed on one competing product, and ChatGPT Business would benefit from an equivalent.
The post ends by asking OpenAI to log the request and pass it to the ChatGPT Business product and engineering teams. It also invites other owners and admins to share similar experiences, since concrete examples would help show the need and inform prioritization.
What to watch
- Does OpenAI respond to the request or add an owner-only invitation setting?
- Will an invitation history showing who invited whom be offered to owners?
- Does Anthropic's documentation describe the invitation setting the way the post says it does?
Try it
If you administer a ChatGPT Business workspace, review the member list for accounts you don't recognize and confirm who holds owner and admin roles. Also check your settings for any invitation control.
Sources and links
Liked it? Say why
Add a line for other readers.
No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.
Listen to the AI Wire headlines
Listen to the AI WireListen to our daily AI shows every morning: on your commute, in the shower, wherever you are
Listen to the daily showsFirst reported by community.openai.com · Read the original. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.
