Multiple Accounts in ChatGPT Plugins: Setup and Limits

Multiple accounts in ChatGPT plugins gained broader support on September 17, 2026. OpenAI says the update extends beyond Gmail, Google Calendar and Google Contacts, letting people use personal and work accounts in one conversation. The announcement covers all ChatGPT plans on web, mobile and desktop; individual app requirements still apply. Official release notes.

Multiple accounts in ChatGPT plugins: what changed

The practical change is a wider set of opportunities to connect more than one provider account. OpenAI’s account-management instructions make the qualification explicit: multiple connections depend on the app and your account. An announcement spanning all plans does not establish that every integration accepts a second login.

Our recommendation is to begin with a concrete retrieval task. Identify the service, the two accounts and the information each should contribute. That gives you a useful test of the feature’s value before you spend time connecting services. A task such as comparing two approved schedules has a clearer success condition than asking ChatGPT to organize everything across your accounts.

Why settings may say Apps or Plugins

OpenAI distinguishes the two terms: an app connects to an external service and its data or actions, while a plugin packages workflow capabilities, potentially including apps and skills. The directory moved toward Plugins, but underlying app connections and their controls remain relevant. Apps and plugins explained.

The setup instructions explicitly accommodate either Apps or Plugins labels. Installing a plugin does not by itself finish the app’s authorization. For a second account, use the controls available for that particular connection. Connection guidance.

This distinction is useful when describing a problem to your administrator. Our suggested issue report names the visible plugin, the underlying service and the provider account you intended to connect. Include the exact message shown at the failed step. “Plugin installed” and “the intended account can retrieve the document” are different observations, so record them separately.

How to connect another account

OpenAI documents this route:

1. Open Settings and choose Apps or Plugins.
2. Select the relevant app or plugin.
3. If offered, open Connected accounts and choose Connect another account; otherwise inspect the displayed Connection section.
4. Sign in and complete the requested authorization.

When supported, you can specify the desired account in your request. Provider authorization does not override workspace restrictions or the connected account’s existing permissions. Official account steps.

For a first check, we suggest asking for one known item from one account. Confirm that the result belongs to that account before broadening the request. Repeat with the other account. If the second connection fails, keep the first result as evidence of what works and note where the second attempt stopped.

Do not assume identical names identify identical content. Two accounts might contain documents with the same title. Include a date, owner or other distinguishing detail in the request, and inspect the returned source. This is an editorial testing recommendation, not a claim that account selection has been tested on your integration.

Keep permissions and data boundaries visible

App availability can depend on plan, region, workspace, role, model and interface. Administrators can restrict accounts to approved domains where that control exists, and supported actions depend on configuration. Connected services also apply their own privacy terms. Availability and controls.

OpenAI says Business, Enterprise and Edu app information is not used for model training by default. For Free, Plus, Go and Pro, information accessed through apps may be used when Improve the model for everyone is enabled. Data-use explanation.

For teams, our recommendation is to agree on the intended account pair and task before trying a combined request. Decide which source material belongs in the resulting answer and who should receive it. An account connection should have a clear purpose. For related administrative background, our Enterprise controls update covers workspace access investigations.

An example request across two accounts

Here is an original, untested example for a supported calendar integration: “Compare tomorrow’s events from my named work and personal accounts. List overlapping time blocks, identify the source account for each event and do not change either calendar.”

Evaluate the response in two passes. First, check each event against its source account and confirm the date and time zone. Second, inspect the claimed overlaps. This separates a wrong source selection from a mistake in comparing times.

If the result is useful, you could then ask for a proposed schedule adjustment as text. Assess that proposal before requesting any supported action. The example deliberately defines a narrow output so you can see whether the connection handles the information you expected. It does not promise support for a specific calendar provider or permission setting. Our prompt library offers further examples of tasks with explicit outputs and review criteria.

Reconnecting and disconnecting are separate decisions

Reconnecting one account does not update every connection. Disconnecting stops future access through that account, while other connections can remain active. Uninstalling a plugin can disconnect all its accounts. Existing conversations, saved files and memories are not automatically deleted by disconnection. Account-management boundaries.

Our suggested final check is to compare the account list with the task you intended to enable. Keep the connections that serve that purpose and review any removal warning before acting. Record the result of the small retrieval test as well: a visible connection is useful setup evidence, while a correctly sourced answer shows whether the intended workflow actually works.