ChatGPT Dots Computer Access: Cloud Browser, Sign-Ins, and Local Machines
A dot's access isn't one switch. Map the cloud computer, website sign-ins, your own computer, and apps, then review and offboard each one.

Most teams treat giving a dot access as flipping one switch. It is actually at least four separate decisions: the cloud computer and its browser, website sessions and saved logins, your own computer, and connected apps. Each has its own settings, its own failure modes, and its own offboarding step. Add a messaging channel and you have five connections, but messaging alone grants none of the others.
This guide maps those connections, shows you how to supervise the cloud computer, explains how website sign-ins work without sharing passwords in chat, tells you when to connect your own computer and when not to, clarifies what Offline and Revoke actually mean, and gives workspace admins the configuration path and policy decisions they need to make before anyone connects anything.
By the end you will have an access map, decision rules for each connection, and a review checklist you can use at offboarding or any time you need to audit what a dot can reach. If you need the full implementation frame including responsibility briefs, custom rules, and a 30-day rollout, start with the ChatGPT dots implementation playbook.
The Access Map: Four Connections Plus Messaging
A dot can connect to five things. Only one of them is required.
The Cloud Computer and Browser
Every dot lives in the cloud with its own computer and browser. This is not your laptop. It has its own files, its own software, and its own browser sessions. The cloud computer stays available when your devices are off. You can send a request from your phone while the dot works in the cloud or coordinates work on a connected computer. The cloud computer keeps its state between periods of use, so a dot can pick up where it left off.
The cloud computer is always connected. The access decision is which capabilities to enable: using a browser, allowing network access, allowing computer use. In Enterprise workspaces, admins control those capabilities (Use a browser, Allow network access, Allow computer use).
Website Sessions and Saved Logins
Signing in to a website on your laptop does not sign your dot in. The cloud browser is separate. When a dot needs access to a website, it sends you a private sign-in form. You enter credentials and any verification code. The form sends the information to the remote browser outside your conversation. The session stays available until you sign out or the site expires it.
You can optionally save the login with Save to Passwords. A saved login is different from an active session. The dot can keep using a valid session without signing in again. Reusing a saved login to sign in requires your confirmation.
Some sites block cloud browsers or require additional verification. In those cases you can sign in yourself by taking over the dot's browser, or ask the dot to try your connected computer if you have one.
Your Computer
Connecting your computer is optional. It unlocks local files, code, apps, your signed-in browser context, local Work or Codex tasks, and local skills. A dot can connect to one personal computer at a time. The connection persists between tasks and applies wherever you message the same dot, including from your phone. Your computer must stay online with the ChatGPT desktop app open. If it goes offline, the dot cannot proceed with work that needs that computer, but the saved grant remains.
Connecting your computer is separate from connecting a computer to Codex or enabling Work Sync. Neither of those alone gives the dot access.
Connected Apps
A dot uses supported plugins that are installed and enabled for your account. Access depends on the plugin's connected account, the permissions you granted, and the environment where the work runs. Existing ChatGPT app permissions apply. You can allow a dot to read email without allowing it to send email. If a connection expires, you will need to reconnect it. Local skills require a connected computer.
The connected account is whose permissions get used. A shared or agent-owned connection can reach things the person making the request could not. That is general ChatGPT connection guidance. Limit scopes before enabling a shared connection.
Messaging Channels Grant None of These
Connecting a messaging channel lets you talk to your dot and get updates. It does not connect your inbox, your apps, or your computer. You still need to make each of those decisions separately.
Questions to Answer Before You Connect Anything
Before you enable any connection, answer these questions:
- Which cloud computer capabilities does this dot need: browser, network access, computer use?
- Which websites will the dot sign in to, and with which accounts?
- Does the dot need access to files or apps on a specific computer, or can it work entirely in the cloud?
- Which plugins will the dot use, and what permissions should each connected account have?
- Who reviews actions before they happen, and who reviews the activity log after?
- What happens at offboarding: who signs the dot out of websites, disconnects apps, and revokes local computer access?
The Cloud Computer: Supervise Without Taking Over Every Time
The cloud computer is where most dot work happens. It keeps state, so a dot can download a file, run a script, open a document, and come back to it later. It can start separate cloud threads that appear in your desktop, web, and mobile apps. For coding, it can use a Codex cloud environment you have set up. It works on several things in parallel.
You can inspect the cloud computer without taking control. Open the dot's profile and select Computers, or select Open computer when the dot offers a browser handoff. Opening the computer shows you what is happening. It does not give you mouse or keyboard control.
When you need to take control, select Take over. You can use the mouse and keyboard. When you are done, select Return control. If you signed in to a website yourself, select Done after you finish.
The decision rule for when to step in: take over when you need to sign in yourself, when you need to verify something the dot cannot verify, or when you need to complete a step the action review flagged as something you must do yourself, such as changing a password. Otherwise, let the dot work and review the activity log. For more detail on connecting computers and apps, see OpenAI's guide to connecting computers and apps to your dot.
Website Sign-Ins Without Sharing Passwords in Chat
The private sign-in flow keeps credentials out of your conversation. When a dot needs access to a website, it sends a request with a private form. You enter your username, password, and any verification code. The form sends the information directly to the remote browser. The credentials do not appear in the chat.
The session can stay available for later work until you sign out or the site expires it. The cloud browser does not inherit logins from your personal browser. If you are signed in to a vendor portal on your laptop, your dot is not signed in to that portal unless you sign it in separately.
When offered, Save to Passwords lets you save a login. If a matching saved login is available for a new sign-in request, you confirm you want to use it or enter another account. A saved login is not the same as an active session. If the session is still valid, the dot can keep using it without signing in again. If the session expired, the dot will ask to sign in, and you can confirm the use of the saved login or enter credentials again.
Some sites block cloud browsers or require additional verification. When that happens, you can sign in yourself by taking over the dot's browser. Or, if you have connected your computer, you can ask the dot to try your connected computer. That may create a separate local task. It does not transfer the cloud session, and it does not guarantee that a particular local browser is supported.
Operator guidance: sign the dot in with the least-privileged account that can do the work. If the site supports role-based or dedicated service accounts, use one of those instead of your personal admin account. Sign out when the work is done, especially at offboarding. Never paste credentials into the chat. Use the private sign-in form or take over the browser and sign in yourself.
Which accounts to sign in: if the dot needs to check order status in a vendor portal, sign it in with a read-only account or a shared account that has only the permissions the dot needs. If the dot needs to update a project management tool, sign it in with an account that has write access to the relevant projects but not to billing or user management. If the site does not support granular permissions, consider whether the dot should have access at all.
When to sign out: at the end of a project, when the dot no longer needs access to that site, and always at offboarding. Signing out of a website is separate from revoking the dot's access to your computer or disconnecting apps. You need to do all three.

Connecting Your Own Computer: Default to Cloud
Connecting your computer unlocks local files, code, apps, your signed-in browser context, local Work or Codex tasks, and local skills. It also introduces new constraints. Your computer must stay online with the ChatGPT desktop app open. If it goes offline, work that needs that computer cannot proceed. A running local task does not automatically migrate to the cloud. A local child task that loses access cannot resume on that computer and is not moved to the cloud automatically.
The connection applies wherever you message the same dot, including from your phone. If you connect your office desktop and then message the dot from your phone, the dot can still access that desktop as long as it is online with the app open. You can connect only one personal computer at a time. The cloud computer stays connected regardless.
The steps to connect: open the dot's profile in the ChatGPT desktop app on the computer you want to connect, select Computers, then Your computer, then Allow access. Review the confirmation and select Allow access again. You must update the ChatGPT desktop app to version 26.929 or higher for local computer access to take effect.
The decision rule: default to the cloud computer. Connect your own computer only when you have a named need for local files, local apps, or your signed-in browser context. If the dot can do the work in the cloud, let it. Connecting a computer adds a dependency and a failure mode.
Picture a five-person accounting firm. The managing partner creates a dot to prepare monthly reports. The reports pull data from a cloud accounting system and a Google Sheet. The dot can do all of that work in the cloud. The partner does not connect a computer. Six months later, the firm starts using a desktop-only tax software package. The partner connects the office desktop so the dot can access the software. The connection is for a named need, and the partner knows the desktop must stay online during tax season.
When a site blocks the cloud browser, you can ask your dot to try your connected computer. The dot may create a separate local task. This does not transfer the cloud session. It does not guarantee that a particular local browser is supported. It is a fallback, not a primary workflow. If you find yourself using the connected computer to work around cloud browser blocks regularly, consider whether the site should be accessed through an API or a connected app instead.
Offline, Revoke, Disconnected, and What Happens to Running Tasks
Offline means the computer is unavailable. The saved grant remains, but work that needs that computer cannot proceed. When the computer is back online with the ChatGPT app open, work that needs it can proceed.
Revoke access removes the grant. The dot can no longer access that computer, even when it is online. Revoke is the setting you use when you want to remove access permanently or switch to a different computer.
Disconnected means access has been removed. It is different from Offline. Offline is a temporary state. Disconnected is the result of revoking access.
What happens to running tasks: a running local task does not automatically migrate to the cloud when the connection changes. If the computer goes offline or access is revoked, the task may be interrupted or the runtime may reload. A local child task that loses access cannot resume on that computer. If an admin disables local computer access for dots, an already-authorized local task may still be finishing. Do not assume that disabling access stops all local work immediately. Check the activity log to confirm tasks have stopped.
Connected Apps Set the Real Limits
A dot uses supported plugins that are installed and enabled for your account. The plugin must be connected to an account, and that account must have the permissions needed for the work. Existing ChatGPT app permissions apply. You can allow a dot to read email in Gmail without allowing it to send email. You can allow it to read and update documents in Google Drive. You can allow it to investigate an issue in GitHub and prepare a pull request.
If a connection expires, open the request to reconnect it. The dot cannot use an expired connection. Reconnecting is a manual step.
The connected account is whose permissions get used. If you connect a shared account or an agent-owned account, the dot can access things the person making the request could not. That is general ChatGPT connection guidance. Limit scopes before enabling a shared connection. If you connect a personal account, the dot uses your permissions. If you connect a service account, the dot uses that account's permissions.
Proactive research tools are read-only. They cannot send messages, change app content, or control your browser or computer. Before an action that could affect accounts or share information, an automatic review checks the action against instructions, permissions, custom rules, and built-in safety requirements. The review decides whether to proceed, whether the action needs your approval, or whether it is a step you must do yourself. For example, changing a password is a step you must do yourself.
Asking a dot to draft replies does not give it permission to send them. You can give scoped instruction that covers future actions within that scope, but the instruction does not override safety requirements or grant access the connected account does not have.
Enabling dots does not give the dot access to every shared drive, channel, or document. An app can be available while some actions still need approval. Read access may not include edit or share permissions. Check the permissions for each connected account. Review them before you connect the account, and review them again if the dot needs to do something new.

What Workspace Admins Control
Role-Based Access and the Default-Off Rule
Dots are off by default in Enterprise workspaces until an admin enables them. In the Admin Console, go to Permissions and look for Use dots. You can enable dots for the workspace default or for specific custom roles. If one role grants access, turning it off in another role will not remove it. The safe pattern is to keep the workspace default off and grant access through a custom role for selected groups. Check every role to confirm who has access.
Related permissions include Add dots to Slack and Microsoft Teams, Allow local computer access (a separate admin opt-in, found under Use dots), and Use custom rules for dots. Members still complete their own Slack and local-computer setup after admins enable access.
Cloud Computer Capabilities
Under Permissions, look for Workspace capabilities and then Let agents use cloud computers. Three toggles control what the cloud computer can do: Use a browser, Allow network access, and Allow computer use. These capabilities are shared by dots, Work Cloud, and team automations. Enabling dots may prompt you to turn on capabilities that are still off.
Use password manager is a separate workspace capability. It governs password manager access in the local in-app browser and the cloud browser. It is not grouped under Let agents use cloud computers, but it affects website sign-ins.
OpenAI's cloud security guidance says to review browser access and code or shell network access separately, because disabling one does not automatically disable the other.
Local Computer Access Opt-In
Allowing local computer access requires admin opt-in and user action. First, in the Admin Console under Permissions, enable dots for the intended users. Then, under Use dots, turn on Allow local computer access. Review the confirmation modal. You can open Agent Security settings from the modal or confirm and move on. Users must update the ChatGPT desktop app to version 26.929 or higher. Then each user connects their computer by opening the dot's profile, selecting Computers, then Your computer, then Allow access.
For the full enterprise guidance on local computer access, including policy precedence and execution environments, see OpenAI's documentation on local computer access for Work Cloud and dots.
Agent Security Policy: Coordination Versus Execution
Work with local access and dots use cloud coordination. Tool steps can run on a connected computer, but conversations, tool results, and task context do not stay exclusively on the connected computer. This is the coordination versus execution distinction.
Agent Security policy is configured in the Admin Console under Agent security. It replaces the older Policies and Configuration section. You set a global baseline and local overrides. Requirements are limits users cannot override. Defaults are starting values users can adjust within the requirements.
Local execution enforces supported local-execution requirements from Agent Security and device policies, including MDM policies such as filesystem and network restrictions. Only the fields supported by the local executor apply. Cloud execution uses separate execution controls. Dots' cloud computers do not automatically inherit local filesystem and network restrictions. Desktop browser site rules do not become cloud-browser restrictions.
Supported device policies apply to steps that run on the connected computer. They do not apply to the cloud computer. The admin guide says local sign-in, VPN access, and device policies do not automatically extend to the cloud computer.
Data Handling, Residency, and Eligibility
Dots with local access still use cloud coordination. Neither Work nor dots provides strict zero data retention. If a workflow requires no retained data, do not enable it. During the Enterprise beta, dots do not support data residency or inference residency. Dots are unavailable for FedRAMP workspaces, workspaces with EKM, and UAE inference residency. HIPAA workspaces can participate if they meet other eligibility requirements.
If any cloud policy enables enforce_residency, Allow local computer access is unavailable for Work and dots. This is the residency safeguard. If you have residency requirements, confirm current support and limitations with your OpenAI account team before enabling dots.
Hooks and Audit
With managed policy and remote hooks enabled, dots with local access use admin-managed remote MCP hooks. Command or shell handlers, prompt handlers, agent handlers, local hooks, and SessionEnd MCP hooks are not supported with cloud orchestration. A hook callback error or timeout can fail without blocking the tool. Hooks do not provide a complete audit trail.
Cloud orchestration events do not reach your OTel collector. Use the Compliance API for supported cloud records and the Analytics API for usage data. Analytics API usage records and Compliance API records identify dots with client_id = DOTS. Admins should confirm which records are available before relying on exports for an audit. The local executor can still export supported execution events.
A Tiered Access Plan
This is our four-tier recommendation, not OpenAI's. Start at Tier 0 and move up only when you have evidence the dot needs more.
Tier 0 is the cloud computer with read-only apps. Enable the cloud browser and allow network access. Connect read-only plugins whose app permissions allow reading but not sending or editing (for example Gmail allowed to read email but not send). The dot can research, analyze, and report. It cannot send email, edit documents, or change records. Run Tier 0 for at least two weeks as a suggested checkpoint. Review the activity log daily for the first week, then weekly.
Tier 1 adds website sessions for named sites. Identify the two or three websites the dot needs to access. Sign the dot in with a least-privileged account for each site. Do not save the login with Save to Passwords yet. Let the dot use the active session. Run Tier 1 for at least one week as a suggested checkpoint. Review which sites the dot actually used and whether it needed to do anything beyond reading.
Tier 2 adds write actions in named apps with approvals. Enable write permissions for specific plugins. Set custom rules to require approval before taking action. The dot can draft an email and ask you to review it before sending. It can prepare a document update and ask you to confirm. Run Tier 2 until you have reviewed at least ten actions as a suggested checkpoint and confirmed the dot is following instructions and respecting scope.
Tier 3 connects a computer for a named need. Do not connect a computer until you have a specific task that requires local files, local apps, or your signed-in browser context. When you connect a computer, document why you connected it and what the dot is allowed to do with it. Review local tasks daily for the first week.
What evidence earns the next tier: clean activity logs, no unexpected actions, no scope creep, and a named need that the current tier cannot meet. If the dot is working well at Tier 1 and you do not have a reason to move to Tier 2, stay at Tier 1. Access is not a progression you must complete. It is a set of tools you enable only when you need them.
Access Review and Offboarding Checklist
Use this checklist at offboarding or any time you need to audit what a dot can reach.
- Plugin authorizations: review every connected app, check the connected account, check the permissions, disconnect any the dot no longer needs.
- Website sessions: identify every site the dot is signed in to, sign out of each one, review any logins saved with Save to Passwords.
- Local computer grant: if a computer is connected, go to the dot's profile, select Computers, then Your computer, then Revoke access.
- Slack identity: check both the dot's own Slack identity and the member's Slack connection through Plugins, because turning off one doesn't remove access through the other.
- Active tasks: open Activity, review active tasks, stop any that should not continue, review scheduled tasks and cancel any that should not run.
- Delegated tasks: check for tasks the dot delegated to ChatGPT Work or Codex; stop delegated tasks in Activity and cancel recurring tasks in Scheduled.
- Admin roles: check the member's dots access in the workspace default and every role assigned directly or through groups; any remaining grant can keep access enabled. (Dots themselves are not assigned roles.) Decide who takes over any remaining responsibilities.
- Revoking dots access does not disconnect apps or sign out of websites. You must do those separately.
- Deleting a dot is separate from revoking access. If you want to remove the dot entirely, delete it after you complete the access review.
If you see an unexpected action, pause the dot immediately. Open Activity and review the task that triggered the action. Save the task link and the activity records. Check app permissions and computer access to confirm what the dot could reach. Follow your incident response process. Do not assume that pausing the dot undoes completed actions. Check the affected systems and accounts.
Common Mistakes
Treating Messaging as Access
Connecting a dot to Slack or enabling texting does not give the dot access to your inbox, your apps, or your computer. Messaging is a channel. Access is a separate set of decisions. If you want the dot to read email, you must connect Gmail. If you want it to access files, you must connect Google Drive or connect your computer. Messaging alone grants nothing.
Assuming the Cloud Browser Is Logged In Like Your Laptop
The cloud browser is not your browser. It does not inherit your logins. If you are signed in to a vendor portal on your laptop, your dot is not. You must sign the dot in separately using the private sign-in form or by taking over the browser.
Signing In with an Admin or Owner Account
Do not sign the dot in with your admin account, your billing account, or any account that has more permissions than the dot needs. If the dot needs to read a project management tool, sign it in with a read-only account. If the dot needs to update records, sign it in with an account that has write access to those records and nothing else. If the site does not support role-based accounts, create a dedicated account for the dot or reconsider whether the dot should have access.
Leaving a Personal Computer Connected Just in Case
Do not connect your computer unless you have a named need. Connecting a computer adds a dependency. Your computer must stay online with the app open. If it goes offline, tasks that need it cannot proceed. If you connected a computer for a specific project and the project is done, revoke access. Do not leave it connected just in case the dot might need it someday. Default to the cloud.
Reading Offline as Revoked
Offline means the computer is unavailable. The grant remains. When the computer is back online with the ChatGPT app open, work that depends on it can continue. Offline is not the same as revoked. If you want to remove access, you must revoke it. Do not assume that a computer going offline removes the dot's access. It does not.
Assuming Local DLP, VPN, or Device Rules Cover the Cloud Computer
Supported device and MDM policies apply to steps that run on the connected computer, and local sign-in, VPN access, and device policies do not automatically extend to the cloud computer. The cloud computer uses separate execution controls. If you need to restrict what the cloud computer can reach, use the cloud computer capability toggles and connected app permissions. Do not assume that your local security controls extend to the cloud. They do not.
Enabling for Residency-Bound Data
During the Enterprise beta, dots do not support data residency or inference residency. If you have data that must stay in a specific region, do not enable dots for workflows that touch that data. If any cloud policy enables enforce_residency, local computer access is unavailable for dots. Confirm current residency support with your OpenAI account team before enabling dots.
Forgetting Sessions at Offboarding
Revoking a dot's access does not sign it out of websites or disconnect apps. You must do those separately. At offboarding, sign the dot out of every website, disconnect every app, revoke local computer access, and remove any Slack connection. Each is a separate step. Missing one leaves access in place.
How SumoGrowth Labs Helps
SumoGrowth Labs is an AI implementation and consulting agency. We help teams map access, design account and connection strategies, configure admin policies, and build review routines. If you need help deciding which capabilities to enable, which apps to connect, or how to structure access tiers and offboarding checklists, we can walk you through it. We implement the configuration and train your team to supervise and review.
by Darius Gaynor

