ChatGPT dots for Enterprise admins: what's known so far

If you run a ChatGPT workspace, you are probably looking for the admin toggle, the policy controls and the audit story for dots. OpenAI has published far less for admins than for individual users. This page separates what is confirmed from what is still missing, and ends with a pilot checklist that is clearly our own suggestion.

What OpenAI has confirmed

Topic	What OpenAI says	Source
Enterprise, Edu, Healthcare	Beta; available when the workspace admin enables it	Announcement, help center
Default state for Enterprise	Off by default	Help center, release notes
Business Premium	Available across all supported ChatGPT regions	Help center
Age	Dots are not yet available to users under 18	Release notes, privacy FAQ
Training on workspace data	Business, Enterprise and Edu data is not used for training by default	Privacy FAQ
Plugin permissions	Shared across dots, ChatGPT, ChatGPT Work and Codex	Privacy FAQ
Texting beta	Not available in Business or Enterprise workspaces	Help center
Usage during launch month	Dots usage won’t count toward eligible Pro, Business and Enterprise plan allowances for the next month	Help center, release notes
Codex and Work tasks	Tasks your dot starts or manages there count toward usage limits as usual	Announcement

What we could not find

We checked the ChatGPT Enterprise and Edu release notes on September 30, 2026. They contained no dots-specific admin instructions. None of the sources we track document:

• where the admin setting to enable dots is, or whether it can be limited to some users or groups
• whether admins can restrict which plugins dots use separately from ChatGPT
• how dots activity appears in audit logs or compliance exports
• usage terms for each plan after the first month, which OpenAI says it will share later

Points that matter for governance

Plugin permissions are shared. OpenAI’s privacy FAQ says “plugin permissions are shared across dots, ChatGPT, ChatGPT Work, and Codex,” managed from ChatGPT’s Plugins tab. Any plugin policy you already set for ChatGPT effectively applies to dots too. There is no documented dots-only layer. See connected apps.

Deleting a dot doesn’t delete everything. Deleting a dot removes its own context. Files, Codex threads and ChatGPT conversations it created are stored separately and are not deleted, and ChatGPT memories remain. Disconnecting a plugin stops new access but does not remove what the dot already built into its context. See memory and reset.

Oversight is per user. OpenAI documents an Activity View on desktop that shows ongoing and delegated tasks and the steps taken, plus custom rules that set how a dot acts. Both are described as user controls. OpenAI has not said whether admins can see or set them. See custom rules.

Built-in guardrails apply everywhere. Changing a password or transferring money always requires the user to take over. Auto-review checks certain actions, such as sending an email, before they happen. Prompt-injection protections reduce the risk but, in OpenAI’s words, “do not eliminate” it.

Specialist dots

The announcement also previews specialist dots, which have their own identity and IT-provisioned hardware. OpenAI says they are “starting with focused enterprise pilots” and that a Microsoft Agent 365 integration is in progress. There is no public sign-up path or availability date in the sources we track. The primary dot described on the rest of this site is separate from this preview.

A rollout checklist for admins

Step	What to decide	Why
1. Pilot group	A small group of users who are 18 or older and comfortable reviewing agent work	Dots are a beta for Enterprise, and every user sets their own rules.
2. Plugin scope	Which plugins pilot users may connect, reviewed in your existing ChatGPT plugin policy	Permissions are shared with ChatGPT, Work and Codex, so a change affects all four.
3. Custom rules baseline	A written default, such as asking before any external email or share and handing off deletes	Rules are set per dot. A shared baseline keeps the pilot consistent.
4. Local computer access	Whether pilot users may connect managed laptops at all	It is optional and off by default. Deciding up front avoids ad hoc grants.
5. Review cadence	A weekly look at Activity View with each pilot user	Activity View is the documented record of what a dot did.
6. Incident path	Who users contact, and when to pause a dot or disconnect a plugin	Disconnecting a plugin stops new access but doesn’t erase what the dot already holds.
7. Usage watch	Track Codex and Work tasks started by dots	Those count toward usage limits as usual, and post-launch terms are not yet published.

Related reading

For plan and region detail, see availability. For how individual users control what a dot can do, start with custom rules and connected apps.