Short version: nothing’s “wrong” on their end — this is rollout + permissions chaos, not user error.
Longer, real-talk version:
That message usually means their Enterprise account hasn’t been provisioned for the new image model yet. OpenAI doesn’t flip features on for all Enterprise orgs at once. Enterprise is actually slower sometimes because features have to be explicitly enabled at the org or workspace level.
A few key gotchas that trip people up:
• Enterprise ≠ auto-access to new models
New image models roll out in waves. Free/Plus/Team often see UI toys first, Enterprise follows once compliance, logging, and billing hooks are ready.
• Admin-level toggle required
Even if the org has access, the admin may need to enable:
the new image model
presets
canvas / space UI
If the user isn’t an admin, they’ll just see… nothing.
• UI mismatch (web vs API)
Some Enterprise users get API access before the ChatGPT UI updates. So the model technically exists, but the interface hasn’t caught up.
• Cached or pinned org environment
Enterprise workspaces sometimes lock users into an older UI version for stability. That kills presets and the “space” layout.
What they should do, concretely:
Ask their Enterprise org admin if the new image model is enabled
Check if the feature is available via API but not ChatGPT
Wait. Annoying, but this is classic staged deployment behavior
This isn’t a skill issue, a payment issue, or a broken account. It’s product ops doing product ops things. Welcome to enterprise software: more contracts, fewer buttons, slower fun.
Bigger picture: Enterprise optimizes for predictability, not novelty. New toys land last, but they land hardened. That’s the tradeoff.