How to use OpenAI dots: plans, regions, usage and permissions

What are dots, and why might an eligible plan lack access?

OpenAI's Meet dots page describes a persistent agent powered by GPT-6 Astra with its own cloud computer and browser. Between conversations, it can continue research, organize material, prepare documents or coordinate tasks, and ask when it needs your decision. This is the official product description, not our availability or reliability test of an account. The page gives no precise release time, so this article uses the September 30, 2026 documentation observation date rather than claiming every user gained access then.

The help page says dots are gradually rolling out to eligible accounts and may take several days to appear. Even a matching plan, age, region and administrative configuration can lack the entry; that does not prove a failed purchase or local-network fault. Check the account and workspace, then look in the ChatGPT desktop app or desktop browser. When mobile access opens, the mobile app can message an existing dot, but at this documentation snapshot it cannot create one. Mobile web does not support dots.

Eligibility differs across Pro, Business Premium and Enterprise

The earlier overview lists Pro 100, Pro 200 and Pro 500 for users aged18 or older outside the EEA, the UK and Switzerland. The current Getting started with your dot help page says Pro more generally while retaining those regional exclusions. Business Premium is described as available in all supported ChatGPT regions. It also says the first dot is included in Pro or Business Premium with no extra fee. Plan and regional eligibility do not mean rollout has reached your account.

The help page says Enterprise, Edu and Healthcare can try the beta after a workspace administrator enables it. Enterprise's dots switch starts off. Check workspace eligibility, your role and access with the administrator; an enabled switch does not prove your account has received the beta. The Enterprise administration document gives a specific permissions interface but does not confirm an identical interface, region or seat scope for Edu and Healthcare. This guide does not ask you to upgrade or change your subscription merely to test an entry.

First setup: start in the cloud, then connect apps and your computer

OpenAI's current help page says to create a dot in the ChatGPT desktop app or desktop browser and finish the introduction. Connect email, calendar or file apps as needed, or skip that step. In the desktop app, you can then decide whether to connect your computer. Windows desktop is also supported. Begin with a small read-only task, such as organizing authorized material into a sourced to-do list, and inspect the result and activity before expanding permissions.

The dot's cloud computer and browser can continue cloud tasks while your device is offline. Local files, code and apps require a separate connection: at most one personal computer may be connected, and it must remain online with the ChatGPT desktop app open. Cloud persistence does not mean local files remain accessible after shutdown.

Authorize apps, chat channels and local access separately

The documentation separates three connections. Slack and Teams are channels for messaging. Connected plugins or apps supply data and operations within their permissions. A computer connection provides access to files and apps on an online device. Adding a dot to a channel does not authorize email, other apps or your computer; connecting a computer does not make every app available. If a website needs login, the dot can make a private login request. Check the destination and requested permissions.

Before enabling writes, specify what the task may read, what it may change, and which sending or purchase actions need your review. A dot may create Work or Codex tasks, which appear in their own task lists and require independent checks of results and permissions. One chat reply does not establish that all background tasks stopped or all changes were undone. Text messaging for US Pro users is a separate limited beta, unavailable to Business and Enterprise workspaces and not offered to every Pro account. Do not confuse it with general dots eligibility.

How Enterprise administrators check switches and roles

In an eligible Enterprise workspace, open Workspace settings > Permissions & roles > Permissions > Workspace default > Workspace capabilities, find Use dots (Beta), save, and check custom roles for the target member or group. The Enterprise switch defaults to off. When someone lacks access, check workspace defaults, direct roles and inherited group roles separately rather than only the global switch. Revocation also requires checking every role that could still grant Use dots (Beta).

Separate permissions by task. Add dots to Slack and Microsoft Teams controls supported chat channels. Allow local computer access controls local files and commands. Use custom rules for dots controls custom rules. The last two default to off in Enterprise. Local access also requires the member to connect an online computer and open ChatGPT. If workspace Codex or ChatGPT Work policy targets a particular operating system, the documentation says local computer access is unavailable; check cloud capabilities separately.

Cloud browser use, Cloud network access and Cloud computer use separately control cloud browsing, network access from code and cloud desktop interaction. Use password manager is another switch. These also affect Work Cloud tasks. Enabling dots does not grant every plugin or website permission; inspect plugin controls, app approvals and third-party authorization separately. The administration document mainly describes eligible Enterprise workspaces; use the actual workspace settings for Edu and Healthcare.

Separate conversation, deeper-work and Work/Codex usage

Meet dots says conversations with a dot do not count toward ChatGPT usage limits. Work and Codex tasks it starts or manages still use their respective limits. The current help page says the first dot is included in Pro or Business Premium without an extra fee; deeper work has a plan allowance, with expanded limits during the first launch month. Public documentation gives no fixed token quantity or daily task count.

Record usage in the actual product pages separately for dot conversations, the dot's own deeper work and delegated Work/Codex tasks. Follow the current plan and workspace settings for allowances and purchase prompts. Unmetered conversations do not imply every agent task consumes no quota, and API token prices cannot be substituted for ChatGPT subscription allowances.

Pause and inspect the main task, delegated work and schedules separately

Control your dot says Pause stops only the current main task. It does not automatically stop every delegated task or cancel future schedules. To stop delegated work, find that task in Activity; disable or delete periodic tasks in Scheduled. Then inspect actual task status and existing outputs. A quiet main conversation is not evidence that every background action stopped.

Deleting a dot does not undo changes already made to connected apps or recall sent messages. If a source, connection or unconfirmed write looks wrong, stop the relevant task, inspect Activity and the destination's actual state, then adjust plugin permissions and rules. Keep important results in reviewable task records. No new messages after stopping does not prove external state was restored.

PuppyIP's boundary: connectivity and plan eligibility are different

For missing access, ineligible regions, disabled workspaces, unauthorized plugins or quota prompts, check the relevant official eligibility and permission information first. A different exit IP cannot add a plan, administrator permission or allowance. PuppyIP may help stabilize access only when evidence points to DNS, TLS, timeouts or proxy407 problems. See the Proxy Connection Troubleshooting Checklist.

This guide records public documentation and practical self-check steps. It has not logged in, created a dot, connected email or verified a reader's account eligibility. If access conditions, allowances or management controls change, follow the documentation and account interface at that time; substantive changes should be reflected in this page.