Go further

Grok Bot: access, data and review

Access, subscription and usage. What you allow, what to do when work stalls and when the job is finished.

In short

  • Access depends on your account type and plan. Check it before you buy.
  • When approving, look at the specific target, account, recipient, content and scope of the change.
  • Auto Review is not a safety guarantee.
  • If a Bot looks idle, check its last question and approval request. It may be waiting for you.
On this pageAccess, subscription and usageWhat you allow and what happens to your dataWhen work stalls or the result is wrongWhen the job is actually finishedYour first week with a Bot

Access, subscription and usage#

Before buying access or assigning a longer job:

  1. Check which account is signed in and whether you have the new subscription or a legacy linked plan.
  2. Review remaining usage, renewal time and additional-usage settings. Look for Usage & Billing in the app; The X Subscription also shows usage on the Grok dashboard.
  3. Measure a small representative task first. A subscription does not mean unlimited tasks or include purchases from other services.

Use Plans and subscriptions for prices, taxes and account transitions. The original Bot launch article may not describe today’s billing. Linking an existing subscription and unifying accounts under The X Subscription are different steps.

What you allow and what happens to your data#

Before approving, inspect the destination, account, recipient, content and scope of the change. “Send these three reviewed drafts to these three recipients” is clearer permission than “handle my email”. Review again if the recipient or content changes.

Use sample or sanitised data for practice tasks. Connect a service only when a task needs it. If you also enable work on your own computer, assess that access separately from the Bot’s cloud computer.

When you stop using it: save results first, pause unwanted routines and review active connections. When revoking access, also check authorisation at the connected service. Deleting a conversation, disconnecting an app and deleting an account are different operations.

For company data, have the administrator approve settings under your organisation’s rules. This guide does not certify that a particular deployment meets your contractual or legal requirements.

When work stalls or the result is wrong#

ProblemFirst check
The Bot appears idleLook for a question, approval request or computer prompt. It may be waiting for you.
A service needs sign-inCheck the account and complete authentication through computer takeover.
A routine did not runCheck whether it is enabled, its owner, time zone, source access and usage.
The output sounds convincing but is wrongIdentify the mismatch with the source and ask to correct the existing output.
@bot does not reply on XCheck the regional scope; silence does not confirm task acceptance.
A button from an old video is missingCompare your version, platform and the current changelog.

To stop work immediately: send the Bot a direct Stop now instruction. This does not undo completed changes. Inspect what happened before deciding how to repair it.

Do not start a computer repair with a reset. The official troubleshooting guide starts with simpler recovery steps; resetting can lose recent unsaved work. Give support the app version, time and time zone, and exact error without passwords or private material.

When the job is actually finished#

The Bot’s closing message is only one place to check. Inspect the deliverable and the state of the service where the work happened.

  1. Open the result: the file downloads and includes the promised sheets, attachments or sections.
  2. Check a sample: open two sources, recalculate one total and inspect an exception.
  3. Verify changes: when a service was updated, inspect the correct account, record and value. A draft is not a sent message.
  4. Read the limits: missing information should be marked, not silently guessed.
  5. Record the next step: who receives the work and what still needs a person.
Run a final check. Return links to finished files, the changes actually made, sources used and unresolved items. Label each item “complete”, “draft ready” or “unsuccessful”. Do not send or publish anything new.

Your first week with a Bot#

This is our suggested practice plan, not a product feature or a performance promise.

  1. Day 1: create one Bot and complete the notes exercise. Check every row.
  2. Day 2: try one real task using public material. Define what “done” means.
  3. Day 3: add one necessary service. Review the account, permissions and approval boundary.
  4. Day 4: repeat the workflow with new inputs. Identify instructions that need improving.
  5. Day 5: create a routine only after the result is reliable. Check its first run, usage and pause control.

The task is done when: the output exists, opens correctly, matches its sources, covers the agreed scope and clearly identifies unfinished items. A message saying “handled” is not enough.

Use the Prompt workshop to build further assignments. Find review principles in Complex tasks.

Sources and verification scope

Facts reviewed: 23 Oct 2026 · Editorial update: 24 Oct 2026

Product claims are based on publicly opened sources. We did not personally test a signed-in Slovak account. Prompts are original examples; sample outputs are illustrative.

Search the guide

Try “privacy”, “files” or “subscription”. Accents are optional.