CHATGPT DOT GUIDE / CONTROL

Control what your dot can reach and do.

App permissions, conversation instructions, Custom Rules and built-in safety checks work together, but they do different jobs. Review all four before giving a dot an ongoing responsibility.

By Agent TaskbookPublished Oct 8, 2026Reviewed Oct 8, 2026
01 / CONTROL LAYERS

Permission is not one switch

LayerWhat it controlsWhat it does not do
Connected app permissionsWhich service and actions are available to the dot.They do not define the responsibility or audience.
Conversation instructionsThe current job, sources, update rules and preferences.They do not override built-in safeguards.
Custom RulesOngoing handling of a specific action: act, wait for instruction, ask, or hand off.They do not grant app/computer access or remove mandatory confirmations.
Automatic action reviewChecks an action against instructions, permissions, rules and safety requirements.It does not make the result error-free.
02 / CUSTOM RULES

Use rules for recurring action boundaries

OpenAI documents four intended behaviors: take the specified action without asking; act when you explicitly say so; ask immediately before acting; or hand the action to you. Use conversation instructions for style and update preferences; use a Custom Rule when the approval boundary should persist.

Ask before sending

Suitable for customer, vendor or public messages where recipient and content matter.

Hand off deletion

Keep deletion of shared files, records or accounts as a step you perform yourself.

Act within a narrow scope

Reserve this for reversible actions whose source, audience and limits are precisely defined.

Never assume access

A rule does not connect a plugin, account or computer. Review those permissions separately.

03 / INSPECT

Review Activity and Scheduled separately

Activity contains delegated work, progress, files, results and requests for input. Scheduled contains recurring tasks and their timing. A main dot, a delegated task and a recurring schedule can continue independently, so check each surface when reviewing or stopping work.

After reviewing the activity log, verify consequential results in the original system. A completed task can still contain an error or fail to deliver the intended outcome.

04 / STOP

Pause does not stop everything

  • Pause: stops the dot's current main task.
  • Activity: open and stop an individual delegated task.
  • Scheduled: disable or delete a recurring task.
  • Revoke access: remove a connected computer or adjust plugin permissions when access is no longer needed.

Stopping work does not undo an action already completed. Deleting a dot likewise does not recall messages or reverse changes made in connected services.

05 / PRE-FLIGHT CHECK

Before you allow ongoing work

06 / PRIMARY SOURCES

Official documentation

Custom Rules are instructions the product tries to follow, not a guarantee against mistakes. Built-in safety requirements still apply.