Notion CoachWork smarter.

Global admins can change a ChatGPT user's email

TL;DR

On November 12, 2026 OpenAI let global admins change the email address of an eligible non-SCIM user in Admin Console. It covers ChatGPT Business, Enterprise, Edu, and Healthcare. Both domains have to be verified for that tenant, and OpenAI emails the old address after the change.

Status
Live
Released
Plans
ChatGPT Business, Enterprise, Edu, and Healthcare

What changed

The ChatGPT Enterprise and Edu release notes for November 12, 2026 say global admins can change email addresses for eligible non-SCIM users in Admin Console. The product release notes the same day add ChatGPT Business to that list. The Admin Console help article, which covers the steps, says the same four plans: Business, Enterprise, Edu, and Healthcare.

A workspace owner or admin role is not enough. The help article says the person making the change has to be a global admin for the tenant.

The help article's requirements, which match the limits in the release notes and add two checks the notes do not spell out:

  • Both the current domain and the new domain are verified for the tenant. You can stay on one verified domain or move between domains verified under that tenant. If either domain is verified for more than one tenant, OpenAI has to have reviewed and approved that use
  • The new address does not already belong to another OpenAI account. This flow does not merge accounts or fix a duplicate
  • The user belongs to only one tenant. Workspaces inside the same tenant do not count as extra tenants
  • The account is at least 24 hours old, with up to 2 changes in a rolling 24 hours and 20 over the account's lifetime
  • The change is blocked if it would remove the user's only way to sign in
  • SCIM-managed users stay on the identity provider. Admin Console is for non-SCIM users

After the change, OpenAI sends a notice to the previous email address. The steps in the help article are Users & groups, then Users, then Change email on that user's menu, then Review change, then Change email. Refresh the list and confirm the new address once it says Email changed.

Why it matters

Someone leaving a domain, or a company renaming a domain, no longer needs a second ChatGPT account to keep the history. The change updates the existing account. The help article says not to create a second account when a change fails, because that split is what this flow is meant to avoid.

The notice to the old address is the check for a change the person did not expect. If they think it was a mistake, the article says they contact the organization's administrator or OpenAI Support.

SCIM is the other path, not a shortcut around these limits. The SCIM article says a tenant-wide directory can update the primary email on an account it already syncs, both domains still have to be verified, and OpenAI Support cannot manually change a SCIM-managed address.

Frequently asked questions

Who can change the email?

A global admin, for a non-SCIM user on ChatGPT Business, Enterprise, Edu, or Healthcare. A workspace owner or admin role alone does not grant it.

Can this move someone to a domain we have not verified?

No. The help article says the flow does not support an unverified domain, merging accounts, or resolving a duplicate account.

What happens to a SCIM user?

Update the email in the identity provider. The November 12 notes say SCIM-managed users should keep using that path.

Sources