At a glance
Dots App Permissions: What to Check Before a Task Stalls
When a dot says it cannot find a file or finish a task, start with the specific source it tried to use. A general “you have access” statement does not tell you whether the correct account, app, folder, and allowed action are in place. This checklist helps you isolate the missing link before you repeat a task. For the related guide, see Dots privacy and permissions guide.
Use it alongside our connection troubleshooting guide and OpenAI's current Dots setup article.
Guide
1. Confirm the right account and source
State the app name, account, workspace, document or channel, and the task's expected output. A connected personal account cannot automatically read a company workspace. A working Slack channel does not imply the same access in Teams. Check the exact resource as the connected user would see it.
Guide
2. Inspect the connection and its allowed actions
Open the dot's connected apps and confirm that the plugin is installed, connected to the intended account, and still authorized. A connection may allow reading without changing a file or sending a message. Reconnect when the session has expired. Do not broaden permissions just to silence an error; request only what the task requires.
Guide
3. Separate app access from browser access
A dot's cloud browser has its own sign-in session. Being signed in on your laptop does not sign in the dot. If a site asks for authentication, complete the sign-in handoff or take over the browser as prompted. When a site blocks cloud browsing, local computer access is a separate optional connection, not an automatic fallback.
Guide
4. Check approvals and task instructions
A task can be waiting for your decision even when its sources are available. Open its activity, look for a pending sign-in or approval, and review the rule for the proposed action. Asking for a draft does not authorize sending it. Keep the boundary explicit: what can be prepared, what can be changed, and who approves publication.
Useful retry: “Use only the connected project folder and the named channel. Tell me which files you can open, which you cannot, and what approval or sign-in is needed. Draft the result without sending or changing anything.”
Guide
5. Run a small access test
Ask the dot to identify one harmless document by title and link, summarize one paragraph, and name the account used. If that works, increase scope gradually. If it fails, capture the exact error and the source URL before changing any permissions. For channels, see the Slack workflow guide or Teams workflow guide.
Questions
Common questions
Does connecting an app grant full access?
No. Access depends on the connected account, available content, the plugin, and the permissions granted for each action.
Why can my dot read but not edit?
Read and write actions can have different permissions or approval requirements. Check the app settings and the requested action.
Is my own browser session shared?
No. OpenAI says the dot's cloud browser keeps its own sign-in sessions.
Will connecting Codex connect my laptop?
No. OpenAI documents dot local computer access as a separate connection through the desktop app.
Can a rule bypass a blocked website?
No. Rules do not supply missing account access or override built-in safeguards.
What should I record before asking support?
Note the task, affected app and account, exact resource, time, error, and whether a small read-only test succeeds.