OpenAI expanded Dots to eligible ChatGPT Enterprise, Edu and Healthcare workspaces on November 4, 2026. Personal dots can continue working on tasks between conversations, extending the product’s ongoing-assistant model into more managed organizations.
Workspace administrators have a time-sensitive rollout decision. OpenAI’s release notes describe an admin preview through November 18, with access available by default afterward unless the organization opts out. Eligibility and regional restrictions still apply.
Ongoing work changes the administrative question
An assistant that continues between conversations needs an owner who understands its assignment and can stop it. For a company, the useful starting point is a concrete recurring responsibility, the resources needed to perform it and a way to confirm whether the expected result occurred.
Our operational reading is that ongoing work should be evaluated as a service with a human owner. A team can identify who receives the result, how failures are surfaced and what should happen when the assignment is no longer useful. Those decisions remain important even when the product handles scheduling and continuity.
What administrators can manage
OpenAI says workspace owners and admins can control member access, inspect personal dots and their connections, pause or resume them and review usage and administrative activity. Workspace owners can also delete personal dots. These controls give administrators several points at which to intervene during a pilot.
For an initial rollout, review the connections attached to each proposed assignment and confirm that they match the task’s actual needs. The review should involve the person responsible for the connected data as well as the employee creating the dot. That helps establish who owns continued access when people change roles.
Residency and healthcare eligibility need a precise reading
The release includes data-residency and Enterprise Key Management support, with inference residency in the EU and US. OpenAI also describes HIPAA eligibility in covered workspaces. Third-party services and other features retain their own coverage conditions, so a connected workflow needs an end-to-end review.
Workspaces with UAE data or inference residency are excluded from this rollout. Organizations with residency requirements should check their actual workspace configuration against the current Enterprise documentation, including the treatment of dots created before general availability.
A practical pilot before the preview ends
Choose an assignment with a visible result and a bounded source set. An internal status summary, for example, can be checked against the underlying records by its intended recipient. Record whether the dot ran, whether the information was current and whether the recipient needed to correct it.
Set an explicit review date before November 18. At that point, an administrator can decide which members should retain access, which connections remain appropriate and which assignments should be paused. The deadline is a reason to finish those decisions while the preview controls are still in effect.