You switch from Personal to Team workspace (or between two Team workspaces, or org A → org B on platform.openai.com), close the tab or browser, return later, and you are back on the original org. This is rarely a bug — it is almost always the active-org cookie being session-scoped, a missing “default org” setting on platform.openai.com, or the org switcher writing to localStorage that gets cleared by a privacy extension. The shortest path: set a default org explicitly in the dashboard, then verify the cookie is persistent.
Common causes
1. No “default organization” set on platform.openai.com
The org switcher in the chatgpt.com UI changes the active context per session. The persistent default — the one used on a fresh tab — has to be set separately on platform.openai.com.
How to judge: platform.openai.com → Settings → Organization → look for “Default organization”. If unset or pointing to the wrong org, that is your answer.
2. Cookie is session-scoped, not persistent
When you uncheck “Stay signed in” or the browser cleans session cookies on close, the org-context cookie (oai_org, __active_workspace, similar) gets wiped. Next session reverts to default.
How to judge: DevTools → Application → Cookies → chatgpt.com → look at the relevant cookie’s “Expires” column. If it says “Session”, that’s why.
3. Privacy extension or browser setting clears site data on exit
uBlock Origin “purge cookies”, Firefox Containers, Brave Shields, “Clear browsing data when I close browser” — any of these wipe the org-selection state between sessions.
How to judge: Disable all extensions, set browser to keep cookies on exit, switch org, restart browser. Org persists? Extension or browser setting was the cause.
4. Multiple chatgpt.com tabs racing the org switcher
If two tabs are open and you switch in one, the other may overwrite the new context with the old one on the next API call. The “last write wins” pattern means you may keep flipping back depending on which tab was active last.
How to judge: Close every chatgpt.com / platform.openai.com tab, switch in one fresh tab only, then test.
5. Workspace owner / admin enforces a default
Some Team / Enterprise workspaces are configured by the admin to always land users on the workspace context, overriding any personal default. Mostly common in tight-controlled enterprise tenants.
How to judge: Ask the admin or check Settings → Workspace → “Enforce as default for members”.
Before you start
- Note specifically what you mean by “org”: ChatGPT workspace (Personal / Team) or platform.openai.com API organization. They behave differently.
- Confirm you actually belong to the org you are trying to default to (visible in the switcher dropdown).
- List any browser extensions, privacy modes, or container setups that might wipe site data.
Information to collect
- Browser name, version, profile name, incognito or not.
- All chatgpt.com / openai.com cookies currently set, especially anything containing
org,workspace, oractive. - Whether the issue happens 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 (dropdown screenshot).
- Whether platform.openai.com → Settings → Organization → Default is currently set, and to which org.
- Any “clear on exit” browser/extension settings.
Step-by-step fix
Step 1: Set the default organization explicitly
On platform.openai.com → Settings → Organization → choose “Set as default” next to the org you want as the always-on landing context. This writes a server-side preference, not just a cookie.
For ChatGPT workspaces (Team), the default landing workspace can be selected in the avatar dropdown → check “Make default” if available, or contact workspace admin.
Step 2: Inspect the relevant cookies
DevTools → Application → Cookies → chatgpt.com. Look for and inspect:
__Secure-next-auth.session-token — session token, sets the user
oai_org — active org context (if present)
__active_workspace — workspace context
oai-did — device fingerprintoai_org should have a far-future “Expires” date (months / years). If it shows “Session”, that means the cookie is wiped on browser close.
Step 3: Disable extensions that purge cookies
Common culprits:
- uBlock Origin → Settings → Privacy → “Clear cookies when site is left” → uncheck
- Privacy Badger / Ghostery / DuckDuckGo Privacy Essentials → make sure chatgpt.com is allowlisted
- Firefox Total Cookie Protection / Containers → either disable for chatgpt.com or commit to one container
- Brave Shields → set to “Standard” for chatgpt.com, not “Aggressive”
Restart browser after changing extension settings.
Step 4: Browser-level “clear on exit” settings
Check the browser’s own privacy:
- Chrome → Settings → Privacy and security → Cookies and other site data → “Clear cookies when you close all windows” → make sure chatgpt.com is in “Sites that can always use cookies” if this is on
- Firefox → Settings → Privacy → History → “Use custom settings” → ensure no “Clear history when Firefox closes” with cookies checked
- Safari → Preferences → Privacy → “Block all cookies” must be off
Step 5: Single-tab workflow during testing
Close every chatgpt.com / platform.openai.com tab. Open exactly one. Switch org. Reload. Close browser. Reopen. Check org. This proves whether persistence works in the cleanest case before adding tabs back.
Step 6: Use URL-pinned shortcuts as a fallback
If org persistence is unreliable, bookmark URLs that pin the org:
chatgpt.com/?workspace=ws_xxxxxxxxxxxxxxxxxx
platform.openai.com/?org=org_yyyyyyyyyyyyyyyyThe query string forces the context regardless of cookie state. Make a separate bookmark per org for fast switching.
Step 7: For enforced defaults, talk to the admin
If your workspace admin has set a forced default, you cannot override it on the client side. Ask the admin to either remove the enforcement or change the default to whichever org you actually use most.
Verify
- Switch org, restart browser, open a fresh tab to chatgpt.com → the switched-to org is still active (top-right avatar / sidebar matches).
- Same test on a different device, signed into the same account, lands on the chosen default org.
- Cookie inspection shows
oai_orgwith a non-Session expiry. - The org switcher dropdown shows the same org marked as “Default” or with a star icon.
- A 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 org explicitly the first day you have multi-org access — never rely on “the one I switched to last”.
- Use bookmarks with
?org=/?workspace=query strings for fast deterministic switching. - Use browser profiles to isolate orgs entirely — work profile for work org, personal profile for personal — eliminates the switching question.
- 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 by their personal switches reverting.
Common pitfalls
- Assuming the in-UI org switcher persists across browser restarts — it doesn’t unless backed by a server-side default.
- Switching in one tab while three others are open — race conditions revert the change.
- Using “Clear cookies when site is left” extensions and then wondering why nothing persists.
- Confusing ChatGPT workspaces (in chatgpt.com) with API orgs (in platform.openai.com) — they are entirely separate contexts.
- Treating Personal vs Team switch as equivalent to org A vs org B — Personal is always “self”, not an org.
FAQ
Q: Why does my org reset only after browser restart but not after a tab close? A: That suggests the cookie is persistent within the session but cleared on full browser exit — typical of a privacy extension’s “clear on exit” rule. Audit extensions.
Q: Can I have different default orgs on different devices? A: No, the platform.openai.com default is per-account, not per-device. Use URL bookmarks if you want different defaults per machine.
Q: Does setting the default in platform.openai.com affect chatgpt.com? A: Partially — for API context, yes. For ChatGPT workspaces, the workspace default is set separately in the chatgpt.com avatar dropdown.
Q: Why does the org switcher sometimes hang for 5+ seconds? A: Workspace switching forces re-fetch of entitlements and chat history. Large workspaces take longer. Not a bug, but improves with stable network.
Q: I left a Team workspace but it still appears in my switcher. A: Browser cache. Sign out fully, clear chatgpt.com cookies, sign back in.