OpenAI says a dot can use connected apps through plugins. App access is separate from Slack or Teams as messaging channels and from a connected local computer.
Connect the tools a task truly needs and understand each permission. A useful answer here should expose the route from source to conclusion. Leave uncertain details marked, then decide which next step belongs to you.
Editorial route
Connect an account for a reason
An integration should answer a task-specific question: which document to read, which calendar to inspect, or which repository to edit. A connection is not a standing instruction to monitor or modify everything in that app. Record the selected account and available actions, run a small read or draft task, and only then consider a write operation. The individual guides distinguish messaging channels from data access and show what to review in each service.
Choose a route
Guides in this section
Pick the specific page that matches the work in front of you. Each guide has a flat URL, a concrete review point, and links back to this overview. If the request spans several guides, finish one bounded piece before adding the next.
No matching guide. Try a broader word.
Define the task
How to use this section
Before you open another connection, assemble account, app, purpose, allowed actions. Check whether those materials already answer the question you intend to ask.
A useful deliverable
A limited connection supporting one task. Add a short list of unresolved questions so the reviewer can decide what needs a fresh source.
Worked situation
How this plays out in practice
A weekly status brief might need calendar dates and project documents, but it may not need permission to edit either source. The situation gives you a concrete acceptance check: can you see the tradeoff and the source behind it?
Choose one connection at a time and record the account, available tool actions, and the smallest task that proves the connection works. The result should remain useful when someone checks it with the original document or account open.
A practical sequence
Run a bounded first pass
Identify the exact account, time window, and account, app, purpose, allowed actions. Keeping a narrow first pass makes the result easier to inspect.
Start with one app. Review its available actions, account identity, and permission scope. Give the dot a small read or draft task before enabling wider actions. Request a preview and a short account of how the source material was interpreted.
Close the first pass with do not equate connection with blanket authorization. Record which question you resolved and which one remains open.
Editorial judgment
Where a plausible answer can fail
Do not infer write permission from a successful read. A messaging channel, plugin connection, and local computer each expose a different surface. Ask what evidence would falsify the proposed answer. That question often exposes the missing piece.
A connection does not automatically authorize a recurring monitor or every possible action. Check the actual plugin’s tools and current prompts in your account. 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
If you are new to the product, Get Started & Trust helps establish the account and permission basics before you use this section as a working plan. Use the next page as a new brief when its evidence and approval needs differ.
For a closely related outcome, open Use Dots in Slack. That guide focuses on use Slack as a way to reach your dot and, separately, as a source for permitted work. 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, Use Dots in Microsoft Teams is a better fit: reach your dot in Teams while respecting workspace boundaries. A new deliverable should have its own date, owner, and acceptance check.
Before you reuse this result elsewhere, look at Get Started & Trust 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
Which guide should I open first?
Open the child guide closest to the result you need: a limited connection supporting one task. Start with its inputs and review gate, then come back to this overview for adjacent tasks.
What information matters most for apps & integrations?
Start with account, app, purpose, allowed actions. OpenAI says a dot can use connected apps through plugins. App access is separate from Slack or Teams as messaging channels and from a connected local computer. Give the exact source or account where a decision depends on it.
How do I combine two related workflows?
Define separate results and approval points. A connection does not automatically authorize a recurring monitor or every possible action. Check the actual plugin’s tools and current prompts in your account.
What would a useful result look like here?
A limited connection supporting one task. 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?
Do not infer write permission from a successful read. A messaging channel, plugin connection, and local computer each expose a different surface. 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.
