You switch from Personal to a Business workspace (or between two Business workspaces, or org A to org B on platform.openai.com), close the tab or browser, come back later, and you are back on the original context. This is rarely a bug. It is almost always one of: no server-side default set, a session-scoped active-context cookie that gets wiped on browser close, a privacy extension clearing site data on exit, two tabs racing the switcher, or an admin-enforced default you cannot override from the client.
Fastest fix (90% of cases): set the default explicitly on the server, then confirm the cookie is persistent.
- API org (
platform.openai.com): Profile menu (top-right) → Your profile → User tab → set Default organization to the org you want. URL:platform.openai.com/settings/profile. - ChatGPT workspace (
chatgpt.com): there is no client “make default” checkbox. Your landing workspace follows the account-level default; if it keeps reverting after the cookie check below, a workspace admin has enforced it (see cause 5).
One naming note up front, since the menus changed: ChatGPT Team was renamed ChatGPT Business on 29 Aug 2025 (name-only change, same pricing and limits). If your screen still says “Team,” it is the same thing as “Business” in this guide.
Which bucket are you in?
| Symptom | Most likely cause | Jump to |
|---|---|---|
| Reverts only after full browser quit, not tab close | Privacy extension / browser “clear on exit” | Step 3, Step 4 |
| Reverts even within one session, after a few minutes | Two tabs racing the switcher | Step 5 |
| Reverts on a fresh tab even with cookies intact | No server-side default set | Step 1 |
| Reverts on every device, instantly | Admin-enforced workspace default | Step 7 |
oai_org cookie shows “Session” in DevTools | Session-scoped cookie | Step 2, Step 3 |
Common causes
1. No default organization / workspace set on the server
The switcher in the UI changes the active context for the current session. The persistent default — the one a fresh tab or a new device lands on — is a separate, server-side preference.
How to judge: platform.openai.com/settings/profile → User tab → look at Default organization. If it is unset or pointing at the wrong org, that is your answer for the API side.
2. The active-context cookie is session-scoped, not persistent
When “Stay signed in” is unchecked, or the browser treats the org-context cookie as a session cookie, it gets wiped on browser close. The next session reverts to the server default.
How to judge: DevTools → Application → Cookies → chatgpt.com → check the Expires / Max-Age column for the active-context cookie (oai_org, __active_workspace, or similar). If it reads “Session”, that is why.
3. A privacy extension or browser setting clears site data on exit
uBlock Origin auto-purge, Firefox containers, Brave Shields, or Chrome’s “Clear cookies when you close all windows” all wipe the org-selection state between sessions.
How to judge: disable all extensions, set the browser to keep cookies on exit, switch, then fully quit and reopen. If it now persists, an extension or browser setting was the cause.
4. Two chatgpt.com tabs racing the switcher
If two tabs are open and you switch in one, the other can overwrite the new context with the old one on its next API call. Last write wins, so you flip back depending on which tab acted last.
How to judge: close every chatgpt.com / platform.openai.com tab, switch in one fresh tab only, then test.
5. A workspace admin enforces the default
Some Business / Enterprise workspaces are configured so members always land on the workspace context, overriding any personal default. Common in tightly controlled enterprise tenants.
How to judge: ask the admin, or — if you are the admin — check the workspace’s general settings for an enforced-default / default-member-workspace option. You cannot override this from the client.
Before you start
- Be precise about what you mean by “org”: a ChatGPT workspace (Personal / Business) on
chatgpt.com, or an API organization onplatform.openai.com. They are entirely separate contexts and behave differently. - Confirm you actually belong to the org you are trying to default to (it appears in the switcher dropdown).
- Note any browser extensions, privacy modes, or container setups that might wipe site data.
- Check the OpenAI status page — there was a confirmed incident on 27 May 2026 affecting workspace switching on Android, so rule out a live outage before debugging your own setup.
Information to collect
- Browser name, version, profile name, incognito or not.
- All
chatgpt.com/openai.comcookies currently set, especially anything containingorg,workspace, oractive. - Whether the issue reproduces in a different browser entirely (Safari vs Chrome).
- The exact sequence: which org you start on, what you do to switch, when it reverts.
- All workspaces / orgs you are a member of (a dropdown screenshot helps).
- Whether
platform.openai.com/settings/profile→ User → Default organization is set, and to which org. - Any “clear on exit” browser or extension settings.
Step-by-step fix
Step 1: Set the default explicitly on the server
For the API org: platform.openai.com/settings/profile → User tab → Default organization → choose the org you want as the always-on landing context. This writes a server-side preference, so it survives cookie clears and follows you to new devices.
For the ChatGPT workspace: switch to the workspace you want via the profile icon (top-right) → Workspaces section. There is no per-user “make default” toggle on the ChatGPT side as of June 2026; the landing workspace follows the account/server default. If it still reverts after Step 2, it is either a cookie issue (Steps 2–4) or an admin enforcement (Step 7).
Step 2: Inspect the relevant cookies
DevTools → Application → Cookies → chatgpt.com. Look for and inspect:
__Secure-next-auth.session-token session token, sets the signed-in user
oai_org active org context (if present)
__active_workspace workspace context
oai-did device identifierThe active-context cookie should have a far-future Expires date (months or years). If it shows “Session”, the cookie is wiped on browser close — go to Steps 3 and 4.
Step 3: Disable extensions that purge cookies
Common culprits:
- uBlock Origin → cookie auto-purge → exclude
chatgpt.com(or turn it off) - Privacy Badger / Ghostery / DuckDuckGo Privacy Essentials → allowlist
chatgpt.com - Firefox Total Cookie Protection / Containers → either disable for
chatgpt.com, or always open it in one fixed container - Brave Shields → set to Standard for
chatgpt.com, not Aggressive
Restart the browser after changing extension settings.
Step 4: Browser-level “clear on exit” settings
Check the browser’s own privacy controls:
- Chrome → Settings → Privacy and security → Cookies and other site data → if “Clear cookies when you close all windows” is on, add
chatgpt.comto “Sites that can always use cookies” - Firefox → Settings → Privacy & Security → History → Use custom settings → ensure “Clear history when Firefox closes” does not include cookies
- Safari → Settings → Privacy → “Block all cookies” must be off; in Manage Website Data, do not delete
chatgpt.com
Step 5: Test with a single tab
Close every chatgpt.com / platform.openai.com tab. Open exactly one. Switch context, reload, fully quit the browser, reopen, and check. This proves whether persistence works in the cleanest case before you add tabs back and reintroduce the race in cause 4.
Step 6: Use URL-pinned shortcuts as a fallback
If persistence is still unreliable, bookmark URLs that pin the context. The query string forces the context regardless of cookie state:
chatgpt.com/?workspace=ws_xxxxxxxxxxxxxxxxxx
platform.openai.com/?org=org_yyyyyyyyyyyyyyyyMake one bookmark per org for fast, deterministic switching. You can read the real ws_ / org_ ID from the URL bar after switching manually once.
Step 7: For an enforced default, talk to the admin
If a workspace admin has set a forced default, you cannot override it client-side. Ask the admin to remove the enforcement or change the default to the org you actually use most.
Optional: use built-in account switching instead
If your problem is really “I keep flipping between a personal account and a work account,” OpenAI’s account switcher (rolled out around March 2026) is cleaner than fighting the default. In the account menu, choose Add account, sign into the second account, and both stay live in the same browser. Switching is instant with no re-login. The limit is two accounts active at once per session; for more you still have to sign out.
How to confirm it’s fixed
- Switch context, fully quit the browser, open a fresh tab to
chatgpt.com→ the switched-to org is still active (top-right avatar and sidebar match). - The same account on a different device lands on the chosen default.
- Cookie inspection shows the active-context cookie with a non-Session expiry.
- The switcher dropdown marks the same org as Default (or with a star icon).
- A brand-new browser profile, signed in for the first time, lands on the default org rather than the first one in the list.
Long-term prevention
- Set the default explicitly the first day you have multi-org access — never rely on “the one I switched to last.”
- Use
?org=/?workspace=bookmarks for deterministic switching. - Use separate browser profiles to isolate orgs entirely (work profile for the work org, personal profile for personal). This removes the switching question completely.
- Avoid aggressive cookie-clearing extensions on
chatgpt.com/platform.openai.com. - For admins: document the enforced default in your team wiki so members are not confused when their personal switches revert.
Common pitfalls
- Assuming the in-UI switcher persists across browser restarts. It does not unless backed by a server-side default.
- Switching in one tab while three others are open — the race in cause 4 reverts the change.
- Running a “clear cookies when the site is left” extension and then wondering why nothing persists.
- Confusing ChatGPT workspaces (
chatgpt.com) with API orgs (platform.openai.com). They are separate contexts with separate defaults. - Treating a Personal vs Business switch as the same thing as org A vs org B. Personal is always “self,” not an org.
FAQ
Q: Why does my org reset only after a browser restart, not after a tab close? A: The cookie is persistent within the session but cleared on full browser exit — the classic signature of a privacy extension’s “clear on exit” rule, or the browser’s own “clear cookies when you close all windows.” Audit those first (Steps 3 and 4).
Q: Can I have different default orgs on different devices?
A: No. The platform.openai.com default is per-account, not per-device. Use the ?org= URL bookmarks from Step 6 if you want a different landing context per machine.
Q: Does setting the default on platform.openai.com change which workspace ChatGPT opens in?
A: Only for the API side. The API org default lives in your profile (/settings/profile). The ChatGPT workspace you land in is governed by the account/workspace default, which is separate — switch via the profile icon → Workspaces and, if it still reverts, check for an admin enforcement.
Q: Why does the switcher sometimes hang for 5+ seconds? A: Switching re-fetches entitlements and chat history for the target context. Large workspaces take longer. It is not a failure, just latency, and it is worse on a slow network.
Q: I left a Business workspace but it still shows in my switcher.
A: Stale browser cache. Sign out fully, clear chatgpt.com cookies, and sign back in.
Q: It reverts on every device at once — is that my cookies? A: No. A symptom that follows you across devices is server-side: either no default set (Step 1) or an admin-enforced default (Step 7), not a local cookie or extension.