Manage dots permissions and capabilities

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

A dot is a personal agent in ChatGPT that can take on ongoing work, use connected apps, and delegate tasks to Work or Codex. You choose who can use dots, configure their capabilities, and manage personal dots across your workspace. Members connect their accounts and tell their dots what to work on.

dots security guide

Use the dots security guide for a detailed review with your security team. This admin guide covers workspace setup, access, and day-to-day management.

For current availability, supported plans, and workspace settings, see Manage dots in ChatGPT workspaces.

Find what you need

Enterprise preview and billing

During the preview, admins in eligible ChatGPT Enterprise, Edu, and Healthcare workspaces can enable dots for selected roles. Starting November 18, 2026, members have access by default unless the workspace opts out. Each member chooses whether to create a personal dot.

Eligible Enterprise workspaces can pay a flat rate based on the type of work a dot does or pay based on consumption. The preview is free. Billing for enabled dots begins November 18, 2026. Tasks a dot delegates to ChatGPT Work or Codex threads incur separate charges at the standard rates. See Dots pricing in the Help Center.

Set up dots for work

1. Configure role-based access

Workspace owners manage access through workspace defaults and custom roles. To give selected groups access, keep the workspace default off and assign a custom role to those groups. Check every role assigned to a member: if one role grants access, turning it off in another role won't remove it.

Review these permissions in Permissions:

• Use dots: Allow members to use dots.

• Add dots to Slack and Microsoft Teams: Allow members to connect their dots to supported messaging channels where available.

• 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.

1. Open Admin Console > Permissions.

2. Under Permissions > Workspace default > Workspace capabilities, enable Use dots if it should be available by default; otherwise grant access through a custom role.

3. Set Slack participation and custom dot rules. Local computer access requires a separate admin opt-in; review local computer access setup before enabling it.

4. Under Let agents use cloud computers, review Use a browser, Allow network access, and Allow computer use where your policies allow browsing websites, accessing online services, and interacting with apps. Review both workspace defaults and custom roles.

5. Under Workspace capabilities, set Use password manager according to your workspace policy.

6. Save, then check access for an intended member.

When you enable dots, you may be asked to turn on cloud computer capabilities that are still off. Dots, Work Cloud, and team automations share these permissions. Choose the capabilities your organization's policies allow.

To review them later, go to Admin Console > Permissions > Workspace default > Workspace capabilities > Let agents use cloud computers. Local computer access is a separate opt-in.

Members still need to complete Slack and local-computer setup after you enable access. Supported app connections they've already set up may be available to their dot.

2. Configure app access

A personal dot can use its owner's existing ChatGPT app connections. Through each connection, it can read or change only what the connected account permits and the workspace allows. When setting up access, check:

1. Which apps members can use. Set available apps and allowed actions in Plugin controls.
2. What the connected account can access. Check the account's permissions in the source app. Enabling dots doesn't give it access to every shared drive, channel, or document.
3. When approval is required. Check the connected app's approval setting for the specific action, such as sending a message. Enabling the app alone does not authorize a send. See app permissions for the options.

For example, permission to read a document may not include editing or sharing it. To restrict access to a particular source, check the connected account and app permissions.

For Auto-review and the difference between authorizing a draft and authorizing a send, see approvals and unattended work.

3. Configure communication channels

Members can connect Slack to their dot in two ways:

Turning off a dot's Slack identity doesn't remove its access through the member's connected Slack account. Check both when removing Slack access. For member setup, see Messaging.

Before members connect their dots to Slack

• ChatGPT workspace owner: Enable Use dots and Add dots to Slack and Microsoft Teams 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.

Verify an approved workflow

After configuring access, test the workflow with the member, connected accounts, and computer environment intended for the work. Use disposable documents and test recipients.

1. Check effective permissions. Review workspace defaults and every assigned role. Confirm which apps, cloud capabilities, and local connections the workflow needs.
2. Prepare a draft from an allowed source. Check the source, connected identity, and output. If the workflow uses both a signed-in website and an app connection, check both accounts.
3. Test approval behavior. Use a harmless action and test recipient. Record the instruction, any approval request, and the final state in the receiving service. A written policy alone does not create a product-enforced restriction.
4. Review available records. Check activity and compliance records to confirm which parts of the test you can reconstruct. Document any missing records.

Compare the result with the requirements approved by your security team. Resolve any gaps in required restrictions or records before using the workflow with affected data.

Available admin controls

For cloud-browser site rules and controls still in development, see browser, network, and device access. For connected computers and delegated tasks, see controls by work environment.

Review availability and data requirements

Before enabling dots, review current availability in Getting started with your dot and the workspace notices shown during setup. Review the security guide's eligibility and data requirements for regional, residency, Enterprise Key Management, and HIPAA coverage. Confirm that your workspace configuration, any applicable business associate agreement (BAA), and the intended workflow meet your organization's requirements before enabling access.

Check requirements for the dot itself, tasks it delegates to Work or Codex, and any connected computer. For cloud browser, network, and computer use, see cloud security. For work on employee devices, see local computer access.

Manage dots in your workspace

Open Admin Console > Dots to see the personal dots created in your workspace. Use the inventory to find a dot and review its owner and status, then open its details to manage it.

Review a dot's details

The details include the member who created the dot, its active or paused status, its identity, and its Slack or Microsoft Teams connection status. The identity is the dot's service account, or its dot ID when a service account isn't available. Connection status shows whether a messaging service is connected; the messaging permission controls who can set up that connection.

Pause and resume a dot

Pause a dot from Admin Console when you need to stop it temporarily. An admin pause prevents the member from resuming the dot. Check the inventory to confirm that its status is paused.

Resuming a dot restores its previous user state. A dot that was active becomes active again; a dot that the member had already paused stays paused. Billing stops during the admin pause and resumes if the dot returns to an active state.

Delete a dot

Delete a dot from Admin Console when it should be removed from the workspace. After deletion completes, it no longer appears in the inventory and billing is paused. Deletion removes the dot's context; it does not preserve the dot for later resumption.

Files, Codex threads, and ChatGPT conversations the dot created are stored separately and aren't deleted with it. Review and delete those items in their respective locations when needed. Use pause when you want to preserve the dot and resume it later.

Revoke and restore access

To remove a member's permission to use dots, review the workspace default and every role assigned directly or through groups. Remove every applicable Use dots grant. Turning off one role's permission does not remove access if another role still grants it.

For offboarding, also review the connections and delegated work in Manage access changes.

Monitor usage

Workspace analytics includes enabled-dot counts and total active users of dots. Enabled dots are dots that are not paused. Use these measures together to understand how many dots are enabled and how many people are using them.

For daily reporting by member or workspace, use the Analytics API. The daily usage endpoint /v1/analytics/workspaces/{workspace_id}/usage identifies dots with client_id = DOTS.

Tasks a dot starts or manages in Work or Codex count toward those products' usage limits and appear in their reporting. Include those tasks when reviewing usage. See Work usage and cost for the available controls, and check the current terms for your plan when setting budgets.

Review admin activity and compliance records

Audit logs capture admin actions on dots, including pause, resume, delete, manage, and saved-tier changes. Use these records to review changes made by administrators.

To investigate work a dot has done, use the Compliance API. Supported dots records include user prompts and responses, supported tool-call events, and connected-app MCP calls and results. Dots-attributed records use client_id = DOTS; the agent object includes the dot ID, name, and type when available.

Workspace owners or admins can select their workspace in Admin Console, then open Credentials > Admin keys and create a key with the appropriate available permissions: enterprise.analytics.usage.read for unified usage reporting, or CODEX_LOG access for dots compliance records. Only workspace owners can grant broad compliance or Conversation messages access where supported. Use the Admin API reference to list and download compliance JSONL files and select records with client_id = DOTS.

Check records for an investigation

Compare a harmless test action with the available export records. Check whether they identify the user, dot, initiating request, tool, applicable approval, and result. Record missing fields and events. A requested tool call does not establish that an action completed; use the receiving service's records to confirm the outcome.

Protect downloaded records according to the sensitivity of the messages and connected data they contain.

Manage access changes

When someone changes roles or leaves, check their dot's permissions, connections, and ongoing work:

1. Remove dots access. Check the workspace default and every role assigned directly or through groups. Remove each permission that grants access; any remaining grant can keep it enabled.
2. Check connected accounts and devices. Review plugin authorizations, website sessions, local computer access, and the dot's Slack identity. Each has its own settings.
3. Decide what happens to ongoing work. Review the pause and deletion controls, then check active tasks, recurring schedules, and tasks delegated to Work or Codex separately. Decide what should stop and who should take over any remaining responsibilities.
4. Delete data where needed. Access changes and deletion are separate steps. Follow the deletion process for the dot's context and any files or tasks stored elsewhere.

For adding and removing workspace members, see User lifecycle management. For dots access removal, see Manage dots in ChatGPT workspaces.

Record access-removal results

After completing the access-change checklist, record which permissions, app authorizations, website sessions, computer connections, and messaging identities were removed. Check active work and schedules separately, including work delegated to Work or Codex. Record any work that remains active and its responsible owner.

Removing access does not reverse actions already completed in another service. Check the receiving service when an action needs to be undone.

Respond to an unexpected action

Pause the dot from Admin Console, confirm its paused status in the inventory, and ask the member to review the affected task. Save the task link and available activity records, check the app or computer permissions involved, and follow your organization's incident process. Whether you can undo an action depends on the action and the service.

Help members work well with dots

Help members choose work to delegate and connect the accounts and tools they'll need. Encourage them to tell their dot what to do, when to do it, and who should see the result.

For example, “Prepare a weekly project update for me to review” asks for a draft. “Post the approved update in our team channel every Friday” also gives permission to post. Members should check important results and know how to review activity, change a schedule, and pause their dot. Share Getting started, Tasks and memory, and Controls to help them get started.