Skip to content
Independent guide · Troubleshooting

Dots Not Showing in Your Account

Check rollout and account eligibility when Dots is absent.

Updated 4 October 2026 · Independent of OpenAI

Dots is gradually rolling out in eligible markets and plans. Workspace access can require an administrator; a mobile device is not the creation route.

Check rollout and account eligibility when Dots is absent. The practical question is whether another person could check the result from the materials supplied. If not, narrow the claim or improve the evidence.

First checks

Identify the state before changing anything

What the interface says

Copy the exact error or waiting message, task name, account, and time. An access problem, an approval request, and a usage limit require different follow-ups.

What already happened

Look in Activity and the connected service for partial results. This matters before a retry that could duplicate a message or an edit.

Define the task

What to prepare before you begin

Begin with plan, region, desktop access, admin status; then say which source should win if an older copy conflicts with a newer approved one.

A useful deliverable

Eligibility checklist and a sensible next check. A compact output with evidence is easier to evaluate than a long answer that hides its assumptions.

Worked situation

How this plays out in practice

A person opens mobile web and cannot find the creation option, while the same eligible account may have an entry point on desktop. Use the situation as a test case. If the result ignores its constraint, revise the brief rather than accepting a convenient default.

Confirm plan, market, signed-in workspace, desktop browser or app, and admin enablement. Compare against the current rollout note. Mark the point at which a draft became a human-approved decision. That boundary matters when the task returns.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Start with plan, region, desktop access, admin status. If a collaborator owns one source, identify the approved version rather than guessing from its filename.

2. Request a reviewable draft

Verify the account and plan, open the updated desktop app or desktop browser, and check workspace enablement if applicable. Look for current official availability details. Make the first result a draft with a concise list of open decisions.

3. Decide the next action

Pause where the consequence begins: no guaranteed rollout date. A proposal is useful even when the action is postponed.

Editorial judgment

Where a plausible answer can fail

Purchasing a plan or reinstalling software is a poor first response if the market or workspace has not been enabled. The right review starts with the point most likely to change the conclusion, not with proofreading the opening sentence.

Do not purchase or switch plans on an assumption that access will be instant in your region. Distinguish incomplete evidence from an actual negative finding. Those lead to different next steps.

Where to go next

Connect this result to the right follow-up

The Troubleshooting 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. Related work should inherit only the context it needs. A fresh guide gives you a chance to reset the audience and action boundary.

For a closely related outcome, open Dots App or Plugin Connection Not Working. That guide focuses on find out whether the problem is sign-in, permission, app capability, or account mismatch. 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, Dots Task Stuck or Waiting for Approval is a better fit: inspect the waiting state before restarting a task. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Track Activity and Review Results 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

What should I check before trying again?

Use the scenario on this page as a small test. Confirm plan, market, signed-in workspace, desktop browser or app, and admin enablement. Compare against the current rollout note. Keep a source and a date beside any detail that can change.

What information matters most for dots not showing in your account?

Start with plan, region, desktop access, admin status. Dots is gradually rolling out in eligible markets and plans. Workspace access can require an administrator; a mobile device is not the creation route. Give the exact source or account where a decision depends on it.

How do I preserve the error for support?

Do not purchase or switch plans on an assumption that access will be instant in your region. The relevant access, audience, and consequences determine what you should approve.

What would a useful result look like here?

Eligibility checklist and a sensible next check. 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?

Purchasing a plan or reinstalling software is a poor first response if the market or workspace has not been enabled. 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.