# ChatGPT dots reach Enterprise: what admins need to decide before November 18

OpenAI's dots rollout reaches eligible Enterprise, Edu and Healthcare workspaces. Review November 18 defaults, billing, permissions and residency limits.

By Paras Madan | 2026-11-05


OpenAI has announced general availability of personal dots for eligible ChatGPT Enterprise, Edu and Healthcare workspaces. These agents can continue tasks between conversations, making the rollout a change in how work is carried out, not simply another model in a picker.

The [November 4 release notes](https://help.openai.com/en/articles/10128477-chatgpt-enterprise-and-edu-release-notes) set an important date: the admin preview ends on November 18, 2026. Until then, administrators can enable access or opt out before availability becomes the default.

For organizations already adopting AI assistants, the immediate question is which jobs, data sources and employees should be included in that transition.

## Availability is not automatic setup

OpenAI's [workspace management guide](https://help.openai.com/en/articles/20001554-managing-dots-in-chatgpt-workspaces) says access is off by default during the preview. Enabling it does not create an agent for every member. Each member still completes onboarding, and administrators can use roles to control access.

Local computer access and custom action rules remain off by default for Enterprise. Cloud browser, network and computer capabilities have separate controls. Connected-app permissions also need their own review; enabling dots does not approve every app or website.

That calls for a capability review rather than one blanket decision. A research pilot may need access to a narrow set of documents but no local files. A coding pilot may need a different environment and review process. Decide the intended workflow first, then grant the capabilities it needs.

## November 18 is also a billing date

The [getting-started documentation](https://help.openai.com/en/articles/20001530-getting-started-with-your-dot) describes a free preview from November 4 through November 18. Billing begins on November 18 for enabled dots. Eligible Enterprise customers can use flat-rate arrangements or scaled consumption, while delegated ChatGPT Work and Codex tasks are billed separately at standard rates.

An initial cost review should therefore cover both the agent and work it sends elsewhere. Confirm the actual commercial arrangement with the account team instead of assuming that an existing ChatGPT seat makes continued agent activity free.

A useful pilot should report completed work, review time, corrections and total cost. Counting messages alone will miss much of the effort involved in an agent that works between conversations.

## Residency and healthcare coverage have boundaries

The [residency documentation](https://help.openai.com/en/articles/9903489-data-residency-and-inference-residency-for-chatgpt) distinguishes long-term storage from model processing. New eligible Enterprise dots support specified storage regions and inference residency in Europe and the United States. UAE data or inference residency is unsupported.

Existing dots in workspaces with residency will migrate within 30 days of general availability. New-region support does not establish that an older agent has already moved. Nor does residency require every cloud-computer action or third-party integration to stay in that region.

Healthcare teams should also read the [HIPAA eligibility guidance](https://help.openai.com/en/articles/20001069-hipaa-eligible-products-and-functionality). Dots are covered only within the applicable eligible workspace, BAA and role configuration. A connected service does not acquire the same coverage simply because an eligible agent uses it.

## Plan the stop procedure before expanding access

The management guide makes another useful distinction: pausing a dot does not erase its data, reverse completed actions or necessarily stop separate delegated and scheduled tasks. Offboarding therefore needs checks beyond the agent's visible pause state.

Before November 18, assign an owner for the rollout, document the chosen access policy and test a small set of representative tasks. Include a rehearsal for pausing work, reviewing connected services and locating outputs. The goal is to know what continues, what stops and who can verify the result before the pilot becomes a broader deployment.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help technical founders explain agent products through clear workflows, practical controls and evidence that buyers can evaluate.

[Book a 30-minute call](https://cal.com/paras-madan/30min).