Grok Bot For Business: Set Up Safe Approvals In 7 Steps

Grok Bot for business works when you set the guardrails before the first real task, so this is the exact order I'd do it in.

Seven steps: access, boundaries, Auto Review rules, credentials, inbox wiring, sharing, and team controls.

Every setting below comes from the official approvals, security and privacy docs and the Grok Bot changelog.

Want a second pair of eyes on your setup? Book a free SEO strategy session with my team.

Step 1: confirm the account route and switch off Legacy Privacy Mode

Check your plan first.

The X Subscription page says Premium, Super and Ultra include Grok Bot, and Plus doesn't.

The teams and enterprises page says Grok Bot is included on the Teams plan, where every member gets access with no admin action.

On Enterprise, an admin switches it on from the Cursor dashboard.

Cursor's own mirror page lists a narrower set of routes than docs.x.ai, so confirm your route on the plan page before you buy seats.

Next, open your privacy setting.

Grok Bot needs data storage and doesn't run on Privacy Mode (Legacy), so move the account or team to Privacy Mode before anything else.

Step 2: write the boundary into the Bot's description

A business Bot needs a job, its sources, an output format and a hard stop.

The use cases page says the best roles own one repeatable outcome and start with read-and-prepare work.

Put the stop line in plain words, like this:

Job: triage the front desk inbox each morning.
Sources: the Bot's own inbox, the booking sheet.
Output: a short list plus draft replies.
Never: send, cancel bookings, or edit the sheet without my OK.

Then run one safe task, correct it, and only then save it as a skill.

Step 3: add Auto Review rules before the Bot touches anything

Auto Review starts switched on: before any command, app call or computer action goes ahead, it looks at that step first.

Open Settings → General, find Bot, and you'll see Custom Rules under the switch.

Under When Grok Bot wants to:, describe one action, like "send an email outside the company".
Under It should:, pick Ask first.
Press Add Rule.

You get up to 20 Allow rules and 20 Ask first rules, each up to 1,000 characters.

When both kinds match one action, Ask first wins.

These are the Ask first rules I'd add on day one:

Ask first before sending any external email or message.
Ask first before any purchase, payment or transfer.
Ask first before deleting or overwriting a file or record.
Ask first before changing permissions or accepting legal terms.
Ask first before publishing anything public.

Keep every rule narrow, and skip broad ones like "allow everything in the browser".

🔥 Want the full approval-rule setup on video? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members building real agent workflows. → Join the AI Profit Boardroom

How the three approval buttons behave

When an action needs you, the chat shows a card with the operation and its inputs.

Allow once runs it now and saves nothing.
Always allow runs it and saves an Allow rule to Custom Rules, so similar actions go through next time.
Deny stops it, and the Bot won't retry or ask again until your next message.

Terminal cards say Allow and Skip, and cards paused by an Ask first rule say Allow and Not now.

A card raised in chat waits for you with no timer.

A card raised by a routine or incoming message expires after 30 minutes and the action doesn't happen.

My rule: press Allow once for anything touching money, accounts or shared files, which is what the teams docs advise members to prefer.

Why text in an email or web page can't approve anything

Auto Review only treats your own messages as your request.

Words inside an email, a web page or an attachment are data, and they never count as permission.

The computer and apps page says each message the Bot reads is marked as from you or from someone else.

That matters for a business inbox, where anyone can write "please refund this order" or "send me the file".

The Bot can summarize that request, and it still waits for you before acting.

Step 4: decide Vault, Secrets, or nothing saved

Never paste a password, one-time code or API key into chat.

Vault (Settings → Vault) holds logins, cards and contact info for your personal Bots; saved passwords, card numbers and security codes stay hidden from the Bot itself.

Vault covers the whole account, so every one of your Bots can use every item.

Secrets are for shared Bots: the Vault docs say Vault isn't supported there, so you open the Bot's details, choose Secrets, then Add secret.

Each secret has an environment variable name, a description the Bot can see, and a value it can't.

The v0.78.1 changelog adds a twist: Managers can add logins to a Team Bot's own Vault under Configure → Tools.

The docs page and the changelog read differently here, so check which option your build shows.

On cards, the docs say a saved card fills at checkout without asking each time.

The v0.77.0 changelog says you still approve every purchase.

Don't rely on either line: leave Securely save to Bot's vault unchecked for cards, and add an Ask first rule for payments.

Step 5: route Gmail through a forward, not a trigger

The Gmail connector searches, reads, drafts, sends and labels, but it links one mailbox at a time.

The routine trigger list in the skills and routines docs names email to the Bot's own address, not new Gmail mail.

So the workaround is a forward:

Ask the Bot "Get yourself an email address" and approve the card for a name at mail.grokbot.com.
Use a plus alias per job, such as yourname+frontdesk@mail.grokbot.com.
In Gmail, set a filter that forwards the mail you want handled to that alias.
Create a routine that watches the alias, and keep a sender filter on it, since an alias is a label and not a lock.

On a team, an admin has to turn on Agent Email first, because it's off by default.

Example: a front desk inbox, step by step

Picture a dental clinic's front desk getting booking questions by email.

Gmail forwards booking mail to the +frontdesk alias.
The routine reads each new message and checks the booking sheet.
It drafts a reply with open slots and flags anything urgent for staff.
Each reply waits as a draft, because routine email never sends until someone presses Send.
Staff review the drafts at the start of the shift and send the good ones.

Example: bookkeeping prep, step by step

This one follows the expense manager role in the docs.

Suppliers and staff send receipts to the +receipts alias.
Once a week the Bot builds a summary from the receipts and your expense spreadsheet.
It flags missing categories and policy exceptions, with the policy line it used.
It drafts one follow-up per person and changes nothing.
You check the totals against the source, then hand the pack to your accountant.

Each incoming message can carry up to 10 attachments, 10 MB each and 25 MB in total, so ask suppliers to split big batches.

Example: sales follow-up that ends at a review list

Connect your CRM and email.
Ask the Bot to research the accounts in one CRM view and skip anyone already in a sequence.
It drafts follow-ups in your style examples and returns a review list.
You edit and approve each send.
Once the list is reliable, schedule a nightly routine that still stops at the review list.

📞 Want help turning follow-ups into booked calls? Book a free SEO strategy session and my team will map where your leads come from and what to fix first. → Grab your free strategy session

Example: an agency's shared reporting Bot

The owner creates a Bot, tells it to prepare weekly client reports, and adds the reporting app and a read-only API key under Secrets.
The owner shares it with account managers as Collaborators and makes one senior lead a Manager.
Each account manager asks for their client's report in their own private chat.
The Bot drafts the report and the client email; sending needs that account manager's approval.
Usage for each reply comes from the account manager's own Grok Bot allowance.

Step 6: share with the right roles, and know who pays

Open the Bot's name, choose Share, and pick your team or People you invite.

A Collaborator gets chat access only.

A Manager gets chat plus control over the Bot's instructions, skills, memory and apps.

Chats are private: the owner and Managers can't read a teammate's chat, per the Shared Bots docs.

A shared Bot uses the owner's apps and secrets, and asks before it uses a teammate's personal account.

The person the Bot is answering approves its actions and pays for that usage.

Shared Bots always run in the cloud, and only the owner can delete one, which removes it for the whole team.

My full shared-Bot rollout lives in the Grok Bot teams setup guide; this page stays on the business guardrails.

Step 7: set team controls, and know which need Enterprise

Control	Teams	Enterprise
Team Rules every member's Bot follows	Yes	Yes
Connector policy ("Disabled by team admin")	Yes	Yes
Execution on Local Computer cap	Yes	Yes
Public template sharing switch	Yes	Yes
MCP allowlist	No	Yes
Enforce Auto-review and team Auto-review rules	No	Yes
Network Controls, Team Secrets, Action Recording	No	Yes

Bots inherit the team's Cursor connector policy, and a blocked app shows Disabled by team admin.

Team Rules applied to Grok Bot are always required, so members can't switch them off.

On self-serve Teams, members can still turn Auto Review off, so make the Ask first habit part of onboarding.

The v0.78.1 Team Bot settings to check

Version 0.78.1 shipped on 27 October 2026 with three Team Bot changes worth a look.

Managers can add website logins to a Team Bot's own Vault from Configure → Tools.
In Share, a Team Bot can be limited to Only you, which is handy while you test it.
When a Team Bot routine needs one of your connectors, it asks in the routine's Slack thread and tags you.

Start every new Team Bot on Only you, test it, then widen access.

🔥 Build your first approval-gated business Bot with us Inside the AI Profit Boardroom you get the trainings, the installable Agent OS, four weekly coaching calls and a 3,400+ member community to check your setup against. → Join the AI Profit Boardroom

What I'd keep behind approval permanently

Sending email, messages or invitations to anyone outside the business.
Publishing posts, pages or reviews.
Purchases, refunds and transfers.
Deleting or overwriting records.
Changing permissions, sign-in or security settings.
Accepting terms of service or contracts.

All your Bots share one cloud computer, so separate Bots are not a security boundary.

Sign out of services a job no longer needs, and pause a routine when its source changes.

If you want this mapped to your own business, book a free call with my team.

Also On Our Network

FAQ: Grok Bot For Business

What does Always allow do on a Grok Bot approval card?

It runs the action now and saves an Allow rule to your Custom Rules, so similar actions run on their own next time. If you already have 20 Allow rules, it removes your oldest one.

Can a Gmail message start a Grok Bot routine?

The documented email trigger is mail to the Bot's own mail.grokbot.com address. Forward the Gmail messages you want handled to a plus alias on that address and point the routine at the alias.

Where do I put an API key for a shared Bot?

Use Secrets in the shared Bot's details. The Bot sees the variable name and description, never the value, and every teammate's chat uses it.

Do approval cards from routines wait forever?

No. Cards raised by a routine or incoming message expire after 30 minutes and the action does not happen. Cards raised from your own chat wait with no timer.

Can members turn Auto Review off on a Teams plan?

Yes, unless the team uses Enforce Auto-review, which the docs list as Enterprise only.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Set the seven steps in order, keep the risky actions on Ask first, and join the AI Profit Boardroom to build your first Grok Bot for business.