A dot is a personal agent in ChatGPT with its own cloud computer. Members can assign ongoing work, such as research or recurring updates, then review its progress and results.
Learn more in the ChatGPT dots guide.
Admins decide who can use dots and which computers, apps, and communication channels they can use. Review action and approval settings before enabling access.
For detailed setup and day-to-day use, see Getting started with your dot in the Help Center.
Set up dots for work
1. Configure role-based access
Workspace owners manage access through workspace defaults and custom roles assigned to groups. Review these permissions in Permissions & roles:
-
Use dots: Allow members to use dots.
-
Add dots to Slack: Allow members to add dots to Slack.
-
Allow local computer access: Allow dots to use a member’s local computer.
-
Use custom rules for dots: Allow members to add or edit rules for their dots.
For role creation, assignment, and access checks, see the role-based access control guide.
Before changing cloud-computer controls or Use password manager, review how they apply across dots and Work Cloud.
-
Open Workspace settings > Permissions & roles.
-
Under Permissions > Workspace default > Workspace capabilities, enable Use dots (Beta) if it should be available by default; otherwise grant access through a custom role.
-
Set Slack participation and custom dot rules. Local computer access requires a separate admin opt-in; review Work Cloud access controls before enabling it.
-
Under Cloud computer capabilities, enable Cloud browser use, Cloud network access, and Cloud computer use where your policies allow browsing websites, accessing online services, and interacting with apps. Review both workspace defaults and custom roles.
-
Under Workspace capabilities, set Use password manager according to your workspace policy.
-
Save, then check access for an intended member.
Granting permission does not connect a service or enable computer access. Members complete Slack and local-computer setup; supported existing app connections may already be available.
2. Configure app access
Dots can use supported existing ChatGPT app connections. Set app access and action restrictions in Plugin controls.
3. Configure communication channels
Allow Slack participation for intended members, then have members complete the relevant channel setup.
Communication with a dot is separate from connecting apps that read or send work content.
Before members connect their dots to Slack
-
ChatGPT workspace owner: Enable Use dots and Add dots to Slack for the intended members through workspace defaults or custom roles.
-
Slack workspace owner or app manager: Ensure the ChatGPT app is installed in Slack. Approve app requests if required by your workspace. See Slack’s app approval guidance.
-
Each member: Connect your dot to Slack from its profile. See Message your dot in Slack.
Enabling the ChatGPT permission does not install an app in Slack or connect a member’s dot.
Available admin controls
| Area | Admin capability |
|---|---|
| Access to dots | Grant or revoke dots access through workspace permissions. |
| Cloud and connected local computers | Control Cloud browser use, Cloud network access, Cloud computer use, Use password manager, and local-computer access. |
| Messaging and participation | Enable or disable Slack participation. |
| Connected apps | Set available apps and allowed actions through Plugin controls. |
| Custom dot rules | When disabled, members cannot add or edit custom rules, and saved rules do not apply. |
| Models | Enterprise model controls and defaults do not apply to dots. |
Dots FAQ
Access and eligibility
Does access to dots grant access to apps and websites?
No. Dots access does not grant access to apps or websites. App connections require authorization; website work uses the browser’s signed-in account.
Whose account does a dot use for connected work?
Review the connected account’s permissions in the source service and the cloud browser’s sign-in separately. See Managing app accounts.
Can a dot use a local computer, VPN, or existing sign-in?
A dot’s cloud computer is separate from a member’s local computer. Local work requires a connected, online computer with ChatGPT open and access enabled. Local sign-in, VPN access, and device policies do not automatically extend to the cloud computer.
How do cloud policies affect local computer access?
If any cloud policy has enforce_residency enabled, local computer access is unavailable for dots. Work Cloud remains available. See Work Cloud access controls for the policy requirements.
Actions and ongoing work
Can a dot keep working when the user is away?
Yes. Members can assign ongoing responsibilities. Workspace permissions and approval rules still apply. Local work requires the computer to stay online with ChatGPT open and access enabled.
Proactive research uses restricted tools to read connected apps; it cannot send messages, change content, or control a browser or computer. Acting on findings requires separate user authorization and applicable permissions and approvals.
Who can message a dot or see its results?
Only the owner can direct their dot through a Slack direct message or supported channel mention. Messages from other people do not start work.
A dot may use other participants’ messages as context when its owner brings it into a Slack thread. Anyone with conversation access can see its posts. Context carried across channels does not authorize sharing with a new audience; check recipients before posting work content.
Microsoft Teams access is limited to an invite-only alpha.
Does a dot always ask before sending or changing something?
Auto-review checks proposed actions against the user’s instructions, custom rules, and safety requirements. Drafting a message does not authorize sending it. Keep app authorization, allowed actions, and action approvals separate; see app permissions for approval options.
How do admins revoke dots access?
Revoke dots access through workspace permissions. Review app accounts and website sessions separately; removing dots access does not replace disconnecting an app or signing out of a website.
How do custom rules affect confirmations?
Default rules govern when a dot can act, needs confirmation, or requires user action. They still apply when custom rules are off.
Custom dot rules guide actions and confirmations. When disabled, members cannot add or edit rules, and saved rules do not apply. Dots still follow default rules and explicit user instructions.
Custom rules cannot override built-in safety requirements. Turning them off does not require confirmation for every action; review capability and app approval settings.
What safeguards help protect work done by dots?
Built-in safeguards help defend against malicious instructions and can pause or stop work when monitoring detects a safety concern.
Members can review progress in Activity View and redirect work. Review consequential results before relying on them.
Models and usage
Do existing model controls and defaults apply to dots?
No. Review dots access and capability permissions directly in workspace settings.
How should admins monitor adoption and usage?
Review current usage terms before rollout. Use the Analytics API for available adoption metrics.
Data and compliance
OpenAI does not use ChatGPT Enterprise data to improve its models by default. For OpenAI’s business data commitments, see Enterprise privacy.
What does a dot remember between requests?
A dot can create saved memories, including information from connected apps. Disconnecting an app does not delete information already obtained. Review saved memories and reset options when handling sensitive data or offboarding.
For separate ChatGPT memory settings and deletion steps, see the Memory FAQ.
How can admins investigate work a dot has done?
Use supported Compliance API records to investigate user messages and dots’ replies. Confirm record coverage before relying on it for an audit.