A dot starts with its own cloud computer. Your local computer remains separate unless you connect it. App permissions are controlled through ChatGPT, and optional Custom Rules can require review for specific actions.
Choose which apps and computers a dot may access and when it should ask. A successful workflow ends with something you can verify, not merely a confident summary. Keep the proof and the proposed action side by side.
Define the task
What to prepare before you begin
Before you open another connection, assemble connected apps, action boundaries, audience. Check whether those materials already answer the question you intend to ask.
A useful deliverable
A permission map and review rules. If the evidence is mixed, show the disagreement rather than forcing a false certainty.
Worked situation
How this plays out in practice
A dot asked to draft a customer update may need to read a project board but does not automatically need permission to send email. The edge case is a useful reminder that the right output follows the task constraints, not the most common pattern in similar examples.
Map each input to the connected app and each proposed action to its approval rule. Inspect Activity when the dot requests a decision. The handoff should tell the next person where to look if the cited information is updated tomorrow.
A practical sequence
Run a bounded first pass
Collect connected apps, action boundaries, audience and mark any sensitive material that does not need to leave its current place.
Inspect connected apps, allowed actions, and Activity. Give a task the narrowest source scope that works. Tell the dot to draft external communication and list proposed changes before acting. Save a reference to the original material beside each consequential conclusion.
Close the first pass with no broad access or external disclosure by assumption. Record which question you resolved and which one remains open.
Editorial judgment
Where a plausible answer can fail
A task can quote sensitive context into a broader audience unless you specify the sharing boundary. Review the recipient and content together. Ask what evidence would falsify the proposed answer. That question often exposes the missing piece.
Proactive research uses read-only tools, but assigned work can have authorized actions. Review the permission screen and data controls for your plan. A useful unresolved list should name the source or person who can answer each question.
Where to go next
Connect this result to the right follow-up
The Get Started & Trust hub gives you the broader route and neighboring tasks. Return there when the present job has produced a result, rather than adding an unrelated responsibility to the same brief. A good handoff identifies what has been settled here and what belongs to the next task.
For a closely related outcome, open How to Pause Dots and Stop Delegated or Recurring Tasks. That guide focuses on pause the dot, stop a delegated task, and cancel recurring work separately. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, What Is OpenAI Dots? is a better fit: a plain-language explanation of what OpenAI Dots does and how it differs from a single chat. A new deliverable should have its own date, owner, and acceptance check.
Before you reuse this result elsewhere, look at Features & How Dots Work for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.
Adapt this
Build your own task brief
Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.
Your review
Check before moving on
Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.
0 of 4 checked
Questions
Frequently asked questions
Where should I verify this feature?
Use the scenario on this page as a small test. Map each input to the connected app and each proposed action to its approval rule. Inspect Activity when the dot requests a decision. Keep a source and a date beside any detail that can change.
What information matters most for dots privacy, memory and permissions?
Start with connected apps, action boundaries, audience. A dot starts with its own cloud computer. Your local computer remains separate unless you connect it. App permissions are controlled through ChatGPT, and optional Custom Rules can require review for specific actions. Give the exact source or account where a decision depends on it.
What changes when a connected app is involved?
Proactive research uses read-only tools, but assigned work can have authorized actions. Review the permission screen and data controls for your plan. The relevant access, audience, and consequences determine what you should approve.
What would a useful result look like here?
A permission map and review rules. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.
What is the common failure in this situation?
A task can quote sensitive context into a broader audience unless you specify the sharing boundary. Review the recipient and content together. Review that issue in the actual output instead of treating a polished presentation as proof.
Where can I check the current details?
Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.
Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.
