Business workflow guide
ChatGPT dots: cloud computer, local computer and app connections
Being able to message a dot does not mean it can reach every file or account you use. Map where the work runs and where the source material lives before relying on it.
Three connections with different jobs
OpenAI says a dot has its own cloud computer and browser, which can work while your devices are off. Its browser sessions are separate from those on your personal computer.
Connecting a personal computer is a separate permission. Only one personal computer can be connected at a time, and it must be online with the ChatGPT app open for local work. Supported plugins use their own connected accounts and permissions. A messaging channel is not automatic access to an inbox, app or computer.
Product source: OpenAI's official documentation, checked 9 October 2026.
Make an access map before connecting
| Question | Example answer | What it tells you |
|---|---|---|
| Where is the input? | An approved folder on a laptop | The task depends on that local computer |
| Where should the output go? | A draft in the task conversation | No write access to the supplier system is needed |
| Which account is intended? | The business account agreed by the owner | A personal login is not an acceptable substitute |
| Who reviews it? | The named operations lead | Someone can inspect the original source |
| What if access fails? | Report unavailable and stop | Missing access must not become an invented result |
Why a working chat can still have a blocked task
For a local workflow, ask whether the required computer is available and the necessary application is open. For a connected service, check that the correct business account and permissions are in use. For a website, a sign-in or additional verification may still be needed.
OpenAI documents a private website sign-in flow and browser takeover. Do not paste passwords into an ordinary task brief. Signing in on your own browser does not sign the separate cloud browser in. Some websites also restrict cloud access; a connection is not a guarantee of compatibility.
Product source: OpenAI's official documentation, checked 9 October 2026.
Test the dependency, not just the happy path
As a proposed acceptance test, start with a harmless sample file. Confirm where the task ran, where the output was saved and whether the reviewer can reopen it. Then agree what should happen if that input becomes unavailable: the task should report the problem and stop, not substitute unrelated data.
For work expected to continue overnight, list every local dependency. A cloud-based coordinator does not make a laptop-only file continuously available. You may decide to keep a manual process until the approved source and execution environment are reliable.
A short handover record
- Purpose and named owner of the connection.
- Approved account, source folder and permitted actions.
- Where the work and output should live.
- Local computer requirements, if any.
- Who deals with sign-in or approval requests.
- How access is revoked when the pilot ends.
- A successful sample result and any remaining limitations.