Two identities can stay signed in at once
OpenAI is rolling out account switching to the ChatGPT apps on iOS and Android. A user can remain signed in to as many as two accounts and switch without completing a fresh sign-in each time. OpenAI says chats, memory, settings and subscriptions remain separate for each account, addressing a common source of friction for people with personal and professional identities.
The feature is useful for consultants, students and employees who work across different subscriptions or managed workspaces. Faster switching can reduce the temptation to copy material between accounts or conduct business work in a personal history simply because the correct session is inconvenient to reach. The interface should always make the active identity obvious before a message is sent.
Separation matters more than switching speed
Separation must extend beyond visible chat history. Connected apps, memory, file libraries, plugins, payment details and model-improvement settings can differ between accounts. A switcher should refresh every permission and context source atomically so that a response cannot accidentally draw on material left active from the previous identity.
Mobile notifications create another boundary. The operating system may display message titles or task updates while a different account is open. Users need clear controls over which identity can send notifications, what appears on a locked screen and whether tapping an alert changes the active account before opening the underlying conversation.
Managed organisations still need clear boundaries
For managed organisations, account switching does not replace device policy or workspace governance. Administrators may still need mobile application management, data-loss prevention and rules covering personal accounts on corporate devices. Users should understand that a convenient account selector does not merge entitlements or authorise movement of protected information.
A sensible rollout should test sign-out, token expiry, account recovery and lost-device scenarios as carefully as the happy path. The feature succeeds when it reduces friction without making identity ambiguous. Security history and session controls should identify activity by account and device so users can quickly recognise and revoke an unfamiliar session.
What teams should validate before production
For implementation, teams should record the exact model, software, dataset, connector and policy versions behind every result. Representative evaluation must include normal work, boundary cases, deliberate misuse and component failure, with outcomes separated by user role, data sensitivity and consequence. A strong average should never hide a serious failure in a critical path. Changes should pass the same regression set before promotion, and operators need a documented fallback that preserves evidence rather than silently broadening access or lowering quality.
Procurement and planning should account for the human work required to review exceptions, maintain controls and investigate incidents. Published performance or efficiency claims are useful starting points, but production confidence comes from evidence collected in the organisation’s own environment. A named owner, measurable acceptance threshold, cost model and tested shutdown path turn a promising release into a service that can be governed over time. Where decisions affect safety, rights, money or regulated records, accountable professional review remains essential.
Security and operational evidence
Security review should map every identity, credential, network destination, stored artefact and administrative access path involved in the workflow. Logs need enough context to reconstruct who initiated an action, which evidence was consulted, what the system proposed and what ultimately executed. Sensitive prompts and traces should not be retained merely because they are useful for debugging. Retention, redaction and access must follow the underlying data classification, with a practical process for correcting or removing material when policy or law requires it.
Operational monitoring should measure quality and service behaviour together. Latency, throughput and availability matter, but so do unsupported claims, missed constraints, unsafe tool calls and the rate at which people overturn recommendations. Teams should rehearse dependency outages and partial failures before unattended operation. If a model, connector or external service becomes unavailable, the workflow should fail predictably, preserve its state and tell the user what remains unfinished. Clear degradation is safer than an agent improvising around a missing control.
Transparency should scale with adoption
Organisations should explain the scope and limitations of the deployed capability to the people affected by it. Users need to know when automation is involved, how to challenge an outcome and where a human can intervene. That transparency improves feedback and prevents a pilot result from being interpreted as blanket approval for broader autonomy. Expansion should follow demonstrated evidence, not novelty or pressure to match a competitor announcement. The durable advantage comes from dependable integration, careful measurement and learning that survives the next model or product update.
Finally, teams should schedule a review after real usage rather than treating launch as the end of governance. The review should compare expected benefits with observed quality, cost, incidents and user behaviour, then retire workflows that do not justify their complexity. A service that works well can expand through the same evidence-based process. A service that fails should be narrowed or stopped without losing the records needed to understand why. This feedback loop is what turns experimentation into accountable operational capability.