A dot starts with a person, but in a company it starts with an admin. For ChatGPT Enterprise workspaces, dots are a beta that stays off until someone with the right permissions switches it on, and several other settings decide what each member’s dot can actually do. This guide explains how to set up OpenAI dots for your team: where the switches live, what each one controls, how Slack and Microsoft Teams fit in, how to roll out to a pilot group and how to take access back. Teams that want to pair agent tools with stronger campaign skills can look at the Digital Marketing Course from Universal Business Council.

What are OpenAI dots, and who sets them up?

A dot is an always-on agent inside ChatGPT, powered by GPT-6 Astra, with its own cloud computer. It works across the apps a member connects and keeps making progress between conversations. OpenAI introduced dots on September 29, 2026.

Who controls setup depends on your plan. Business Premium users get dots across all supported ChatGPT regions. For Enterprise, workspace owners decide who can use dots and which capabilities come with them, and the beta is off by default. Each person then creates their own dot in the desktop app or desktop web, so rollout is a shared job: admins open the door and members walk through it.

Where to enable dots in your workspace

OpenAI’s documentation describes the route for eligible Enterprise workspaces:

Open Workspace settings, then Permissions & roles.
Go to Permissions, then Workspace default, then Workspace capabilities.
Find Use dots (Beta) and review the dots permissions and computer capabilities below it.
Save your settings, then review any custom roles that apply to the members you want to enable.

Two permissions sit at the top. Use dots (Beta) lets members use dots at all. Use custom rules for dots lets them add or edit rules that guide their dot’s actions and confirmations. Both are off by default for Enterprise, and the other dots permissions only take effect once a member has access to dots. You can also use custom roles to give specific members or groups different access, which is how most teams run a pilot. Because features are rolling out gradually, some options may not appear in your workspace yet.

Computer, browser and password settings

Dots work from a cloud computer, and admins control what that computer may do. Under Workspace capabilities, a set of cloud controls covers three things:

Cloud browser use, which lets dots and Work Cloud tasks open and interact with websites.
Cloud network access, which lets code and shell commands on cloud computers reach the internet.
Cloud computer use, which lets them interact with the desktop and applications on the cloud computer.

Use password manager is a separate control from browser use. These settings apply to dots even when Work or Work Cloud is disabled, and existing defaults for browser and network access carry over.

Security teams should know that a dot’s cloud computer doesn’t automatically inherit a member’s local VPN, browser sign-ins or device policies. A site that needs a sign-in may require the member to sign in on the cloud computer.

Local computer access is its own setting. Allow local computer access lets a dot use a member’s local files and run commands on their computer, but the member must also connect their computer, keep it online and keep the ChatGPT app open. It’s off by default for Enterprise, and it isn’t available in workspaces with Codex or Work policies that target a specific operating system. In those cases, dots can still work on their cloud computers if the relevant cloud capabilities are on.

Apps, approvals and rules

Enabling dots doesn’t grant access to every app or website. Supported app connections a member already uses in ChatGPT may be available to their dot, but plugin controls decide which apps are available and which actions they can perform. App permissions determine when an action needs approval, and each connected service’s own authorization limits what the dot can reach. Review these settings separately from dots access, along with app authorizations and website sessions, which are managed apart from each other.

Rules deserve a careful read. Default action rules still apply when custom rules are unavailable, custom rules can’t override built-in safeguards, and turning custom rules off doesn’t make every action require approval. In other words, switching off custom rules won’t make the system stricter by itself. Also note that Enterprise model controls and default model settings don’t apply to dots, so your usual model restrictions won’t carry over.

IT staff who will manage these settings may benefit from structured study of programming and AI tooling, such as the Tech Certifications from Global Tech Council.

Slack and Microsoft Teams

The Add dots to Slack and Microsoft Teams permission lets members connect their dots to supported communication channels where available. Turning it on does not install a Slack app or connect anyone’s dot. For Slack, both Use dots (Beta) and the Add dots permission must be enabled for the member. If your Slack workspace requires app approval, a Slack workspace owner or app manager must approve the installation and permissions. Each member then completes their dot’s Slack setup.

Plan for how it behaves in practice. A dot joins the workspace and posts with its own identity. Only the dot’s owner can direct it, so other people’s direct messages or mentions don’t start work, but its channel posts are visible to everyone in that channel. Phone messaging through iMessage, RCS or WhatsApp is unavailable for Enterprise at launch.

Rolling out to a pilot group

A staged rollout keeps problems small.

Start by choosing one team with a clear, repeatable process, and give that group access through a custom role instead of the workspace default. Decide which apps they may connect and which cloud capabilities they need. Leave local computer access off unless a task requires it. Before anyone creates a dot, brief the group on how rules work, what to review and what never to ask a dot to do.

Run the pilot for a few weeks, and gather both numbers and stories. How much time did the work save? What did reviewers catch? Where did the settings get in the way? Then adjust permissions and decide whether to widen access. Leaders tracking how AI, blockchain and other deep technologies are reshaping software buying can read more through the Deep Tech Certifications from Blockchain Council.

How to remove or limit access

Taking access back takes more care than granting it. To remove a member’s access, review Use dots (Beta) in the workspace default and in every role assigned to the member, directly or through groups, and remove each grant that applies. A role that grants access can still let a member use dots even if another role has the permission turned off, so a single check isn’t enough. App authorizations and website sessions are managed separately, so review those too.

Conclusion

To set up OpenAI dots for your team, begin in Workspace settings and work through the switches in order: access, custom rules, cloud computer controls, local computer access, app permissions and Slack or Teams. Everything is off by default for Enterprise, so each capability is a deliberate choice. Remember that default action rules and built-in safeguards stay in place whatever you decide, that model controls don’t apply to dots and that removing access means checking every role. Pilot with one group, measure what changes and widen slowly. Features are still rolling out, so confirm each setting against OpenAI’s current help pages before you announce anything to your staff.

FAQs

1. Who enables dots in an Enterprise workspace?

Workspace owners, through Workspace settings and Permissions & roles.

2. Are dots on by default for Enterprise?

No. Use dots (Beta) is off by default.

3. Where is the main dots setting?

Workspace settings, Permissions & roles, Permissions, Workspace default, then Workspace capabilities.

4. Can I enable dots for only some members?

Yes. Use custom roles to give specific members or groups different access.

5. What does Use custom rules for dots do?

It lets members add or edit rules that guide their dot’s actions and confirmations.

6. What if I leave custom rules off?

Default action rules still apply, and built-in safeguards remain.

7. Does turning custom rules off require approval for everything?

No. It doesn’t make every action require approval.

8. What are the cloud computer controls?

Cloud browser use, cloud network access and cloud computer use.

9. Is the password manager part of browser use?

No. Use password manager is a separate setting.

10. Does local computer access come on automatically?

No. It’s off by default, and members must also connect their computer.

11. What must a member do for local access?

Connect their computer, keep it online and keep the ChatGPT app open.

12. Does a dot’s cloud computer use my company VPN?

No. It doesn’t automatically inherit a member’s local VPN, browser sign-ins or device policies.

13. Does enabling dots open every app?

No. Plugin controls, app permissions and each service’s authorization still apply.

14. Do Enterprise model settings apply to dots?

No. Enterprise model controls and default model settings don’t apply.

15. What does the Slack and Teams permission do?

It lets members connect their dots to supported channels. It doesn’t install an app or connect a dot.

16. Who approves a Slack installation?

A Slack workspace owner or app manager, if your workspace requires app approval.

17. Who can direct a dot in Slack?

Only the dot’s owner. Channel members can see what it posts.

18. Is phone messaging available on Enterprise?

iMessage, RCS and WhatsApp messaging are unavailable for Enterprise at launch.

19. How do I remove a member’s access?

Review Use dots (Beta) in the workspace default and every role assigned directly or through groups, then remove each grant.

20. How should we roll out dots?

Start with a pilot group through a custom role, keep local access off unless needed and review results before widening.

How to set up OpenAI dots for your team: an admin guide to enabling and rolling out dots