Skip to content

Pre-flight security checklist

Before your Bot touches email, money or your team chat, take two minutes to check your setup.

What this tool does

This is a tick-box checklist to use before you connect an email account, a bank login or Slack to Grok Bot. Each item says what to check and links to the lesson that explains it. It’s the interactive version of our printable pre-flight checklist.

It’s for small-business owners about to connect real accounts for the first time. It’s a set of reminders, not a security review or advice for your situation.

How to use it

  1. Open the checklist before you connect a new app or login.
  2. Read each item and tick it once it’s true for your setup.
  3. For any item you can’t tick, open its lesson and fix that first.
  4. When everything is ticked, connect the app (lesson 2.2).

The checklist

  1. Work and personal accounts are separate. Connect a work email, not your personal one. (Spec, section 12)
  2. Bank logins stay off the shared computer. Don’t save bank logins where your Bots can use them. (Spec, section 12)
  3. Every message to the outside waits for your approval. Add an Ask first rule for sending (source), and keep drafts on. By default, Bots draft outgoing email and Slack messages for your review (source).
  4. You know that all your Bots share one computer. Files, browser sessions and logins on it are open to every Bot on your account. Separate Bots aren’t a security boundary (source).
  5. You know that apps are account-wide. A connected app is available to every Bot you run (source).
  6. You know what the Google apps can reach. The Google Drive app can search and read every file the connected Google account can open. The Sheets app can edit any sheet that account can edit (source). Use an account that holds only what the Bot needs.
  7. You know who Slack messages come from. The Slack app posts as the Slack user you connected, in any channel that user can post in (source).
  8. Passwords go in Vault, never in chat. Never paste a password, one-time code or API key into ordinary chat (source).
  9. Notifications are on for Bots that run routines, so you see approval cards before they expire (source).

Runs in your browser only. Nothing you type is sent anywhere; answers are saved in this browser until you clear them.

Check each one

Also read xAI’s approvals, security and privacy documentation before you connect a live account.

Your privacy

This tool runs in your browser only. There are no form submissions, no accounts and no analytics on what you type, and it collects no personal data. Anything it remembers is kept in your browser’s local storage, with a visible Clear button. If JavaScript is off, you see the same content as a readable list or table.

FAQ

Should I connect my bank account to Grok Bot?

This checklist’s advice is to keep bank logins off the shared computer. Lesson 3.9 explains why. We don’t give financial or security advice for your business.

Can I keep accounts apart by using different Bots?

No. All your Bots share one computer and every connected app, so separate Bots aren’t a security boundary (source).

Can other Grok Bot users see my computer?

The docs say isolation between users is strict: each user’s computer is dedicated and hardware-isolated (source).

Does ticking every box make my setup safe?

No checklist can promise that. It covers the common mistakes beginners make. Read Security for the full picture.

Sources