Field notes · AI agents, Hermes & Claude Code By Julian Goldie

Grok Bot Enterprise Explained: What It Is, What It Includes, And A 10-Step Admin Rollout

What the business edition of Grok Bot is and does, followed by the admin order I'd use to switch it on safely.

Get The AI Profit Stack Join AIPB →
  • 01 1,000+ done-for-you AI agent workflows
  • 02 5 live coaching calls / week with me
  • 03 7-day refund, cancel anytime
  • 04 3,400+ AI operators inside

Grok Bot Enterprise is the business edition of Grok Bot: AI teammates that each work on their own cloud computer, shared across your company as Team Bots, with the access, network and audit controls an admin needs to govern them.

xAI announced it on 3 September 2026, and the 11 November 2026 changelog entry added meetings, Microsoft Teams and shared connectors for teams.

This page explains what you're actually rolling out, then gives the ten admin moves I'd make, in order.

The facts come from xAI's teams and enterprises docs, the Team Bots page and the security page.

Planning this for a client or your own company? Book a free SEO strategy session with my team and we'll map the rollout with you.

What Grok Bot Enterprise is

xAI's launch post describes Grok Bot as a team of AI teammates you hand real tasks to, which then carry the job through end to end inside the tools you already use.

Under the hood, the docs call it a computer-use agent: each user's work runs in a dedicated Firecracker microVM in Cursor's cloud, and the desktop and phone apps are where people chat, review and approve.

The enterprise part is governance.

The launch post says the release added access, network and audit controls so companies can run Bots at scale, and admins manage all of it from the Grok Bot page of the Cursor dashboard.

On the Teams plan, Grok Bot is already on for every member and there's no off switch; on Enterprise, nothing runs until an admin enables it.

The features you're rolling out

  • Cloud workers. Each Bot can use apps, a browser and a shell on its computer, and comes back when it's done or needs a decision.
  • Workflow learning. The skills and routines docs describe Teach a task: you perform a browser workflow once and the Bot drafts a skill from it.
  • Team Bots. One shared Bot, a private chat per person, and team learnings that wait for approval.
  • Integrations. Apps such as Slack, Notion, Google Drive and Microsoft Teams, plus custom MCP connectors.
  • Meetings. Bots join Google Meet, Zoom and Microsoft Teams calls and send summaries, on Team, Enterprise and Ultra plans.
  • Admin controls. Team Rules, sharing limits and the Microsoft Teams switch on both plans; SCIM, Network Controls, setup scripts, secrets, enforced Auto-review, inference hooks, audit logs, Action Recording and retention on Enterprise only.

If a step below names an Enterprise-only control and you're on Teams, skip it and move on.

Step 1: Clear the three rollout blockers

The docs list these under "Before you roll out", and each one can stop members cold.

  1. Privacy Mode (Legacy). It blocks Grok Bot completely. Change it in Team Settings, and the enable flow prompts you if you forget.
  2. TLS-inspecting proxies. If devices sit behind Zscaler or a similar gateway, allow Cursor's domains, including the nested *.*.cursorvm.com pattern, and exempt them from inspection on every profile. The proxy guide has the list.
  3. Source-IP rules. Bot computers leave through shared static egress addresses that are shared across Grok Bot customers. Dedicated per-customer IPs aren't offered, so plan your allowlists around that.

Do these first and the members you invite won't hit a setup error on their first day.

Step 2: Flip Enable Grok Bot and scope it to groups

On Enterprise, open the Grok Bot page and turn on Enable Grok Bot.

A setup modal walks you through privacy mode, billing and model availability, offers to switch on Cloud Agents if they're off, and asks you to accept the Grok Bot Terms.

Then open Manage Group Access beside it.

I'd start with one pilot group, not the whole company.

Turning the switch off later blocks every member without deleting their computers, so a pause is cheap.

To bring people in, use Invite Team: existing Cursor users get an email with a download link, and new users get a team invitation.

Step 3: Wire up sign-in and provisioning

There's no separate Grok Bot app in your identity provider.

Members sign in with their Cursor account, so the Cursor SSO you already run applies, and the identity and access guide says Cursor SSO is SAML 2.0 and works with Okta, Microsoft Entra, Google Workspace and OneLogin.

Two changes do two different jobs:

  • Assign the Cursor app to people outside engineering, so they can reach Grok Bot through your Cursor team.
  • Add an authentication rule so members can sign in to company apps from the Bot's computer, which runs Linux and isn't a managed device.

SCIM 2.0 provisioning and deprovisioning is Enterprise only.

If your sign-in policy requires Okta FastPass, the Okta FastPass guide installs Okta Verify on Bot computers through Team Setup Scripts.

🔥 Want the full Grok Bot team rollout 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 comparing the Bot setups they run for their teams. → Join the AI Profit Boardroom

Step 4: Lock the network before anyone builds a Bot

Network Controls is Enterprise only, and teams without a policy default to allow-all.

Find Grok Bot Network Access under Network and pick one of four modes:

ModeWhat it doesWhen I'd use it
Allow All Network AccessNo restrictionNever, once real data is involved
Allow All Sites Except TheseBlocks up to 50 listed sites, subdomains includedA light first pass
Defaults + Team AllowlistDefaults plus the domains and IP ranges you addMost company rollouts
Team Allowlist OnlyOnly the destinations you listTight, regulated teams

Two gotchas.

Blocked sites work on a best-effort basis and the docs say plainly they're not a security boundary, so use an allowlist when it matters.

And connected apps aren't covered until you add their hosts, such as api.github.com or api.x.com, and turn on Apply to MCP servers, which is off by default.

Step 5: Enforce Auto-review, then add team rules

Auto Review is the independent review model that checks risky actions before they run.

Members can switch it off for themselves unless you turn on Enforce Auto-review, which is Enterprise only and off by default.

Turn enforcement on first.

Without it, a Team Bot working in a chat where no one can respond to an approval card runs with no Auto-review at all.

Then open Configure Rules and add team-wide Ask first and Allow automatically rules.

The docs suggest production deployments, external email, payments and accepting legal terms as Ask first examples.

Members see the team rules under Settings → General → Auto-review but can't edit or delete them, and Ask first wins any conflict.

Step 6: Write two or three Team Rules

Team Rules are guidance every member's Bots follow, and rules scoped to Grok Bot can't be switched off by members.

Keep them short and few, like the docs' own example: "never move company data to personal accounts."

Rules steer behaviour, while Auto-review rules decide approvals, so don't try to do approval work with a Team Rule.

On the same page, set Execution on Local Computer to Never allow unless Bots have a reason to touch member laptops; the default leaves it to each member.

Step 7: Prepare computers with setup scripts and secrets

Team Setup Scripts run install manifests on every team computer, so the same tooling is everywhere.

Keep secret values out of the scripts and store them as Team Secrets instead.

Each secret is an environment variable name and a value, stored encrypted and never shown again after you save it.

The limits are 100 secrets per team, 32 KB per value and 96 KB in total.

Team Secrets reach your scripts only, never the Bots directly, and a computer that pulls setup from two or more teams gets no secrets from any of them.

If Bots need private systems, the private networks guide shows how to install your networking client this way.

Step 8: Publish one Team Bot and set the sharing rules

Now build the first shared Bot.

Choose +, then Create a Bot, name it, tell it in one sentence what it helps the team with, and follow its setup for apps, secrets, skills and files.

It stays a draft only you can see until you press Publish.

Before you publish, set three switches under Sharing:

  • Bot sharing: Everyone is the default. Pick Admins only if Team Bots should be reviewed before teammates use them.
  • Allow Shared Logins: off by default. Leave it off unless one Manager's account really must serve everyone, because every user then acts through that account.
  • Slack Workspace Access: on by default. It lets Slack members who aren't on the team use Bots shared with your organization.

The v1.0.1 changelog added the piece I like most: what teammates teach a Team Bot now waits under Review learnings until the owner or a Manager approves it.

Step 9: Connect Microsoft Teams, Slack and meetings

Plan Microsoft Teams as a three-role job.

First, your Cursor team admin presses Enable beside Enable Microsoft Teams, logging in as a Teams administrator or Global administrator.

Next, whoever owns the Bot, or one of its Managers, opens the Bot's details and picks Connect Microsoft Teams.

Then a Teams admin approves it under Teams apps > Manage apps > Pending approval, which Microsoft documents in its Manage apps guide.

Microsoft doesn't notify that admin, so send them the link from the dialog, and allow up to an hour after approval.

My Grok Bot Microsoft Teams walkthrough covers the screens one by one.

Slack is simpler: open the Bot's details, find Bring to your team's Slack and choose Connect.

Meetings are their own switch under Bot Capabilities, available on Team, Enterprise and Ultra plans, and when it's off Bots can't join or read meetings.

For the join flow and the summaries, see the Grok Bot meeting guide.

📞 Want this rollout planned with you? Book a free SEO strategy session and my team will walk your admin settings, groups and Team Bots with you. → Claim your free strategy session

Step 10: Turn on the logs and set retention

Last, make sure you can see what happened.

Audit logs cover admin, security and authentication events plus Grok Bot control-plane events, such as Bot creation, access changes and routines, and you can stream them to your SIEM.

Action Recording is a separate switch, off by default, that records what Bots did: tool calls, shell commands, browser navigations and messages sent.

Those events are sanitized metadata and don't appear on the Audit Log page, so export them through OpenTelemetry to your own collector.

Finally, set Data Retention: Bots after 60 to 365 quiet days, computers after 30 to 365, messages after 30 to 365.

Each is off by default, and deleted data can't be recovered, so start long and shorten later.

The gotchas I'd warn every admin about

  • All of one member's Bots share one computer. A login on it is open to every Bot that member runs.
  • A Team Bot's apps, secrets and files work in every teammate's chat. Add only what you're happy for all of them to use.
  • Group settings only widen the team baseline, except network policy, so tighten on the Grok Bot page and widen per group.
  • Deleting a Team Bot removes it, its Slack app, and teammates' chats and routines on it. It can't be undone.
  • Your team's model allowlist doesn't govern Grok Bot. If you need a check on model requests, use inference hooks, which start in Shadow mode.

My verdict on this rollout order

Blockers, enable, identity, network, approvals, rules, computers, Team Bots, channels, logs: that sequence means no member ever touches a Bot before its guardrails exist.

On Teams you'll skip the Enterprise steps and still get a clean rollout.

Want the same setup on video? The AI Profit Boardroom has the trainings and the Agent OS.

Run the ten steps on a pilot group first, then widen it.

Also On Our Network

FAQ: Grok Bot Enterprise Explained

What is the first thing to do before enabling Grok Bot for a company?

Move off Privacy Mode (Legacy), clear Cursor's domains in any TLS-inspecting proxy, and plan for shared egress IPs. Privacy Mode (Legacy) blocks Grok Bot entirely.

Do I need SCIM to roll out Grok Bot?

No. Members sign in with their Cursor account and your existing SSO. SCIM provisioning is available on the Enterprise plan if you want it.

Can members switch off Auto-review on an Enterprise team?

Only while Enforce Auto-review is off. Turn it on and members can't disable it, unless a group lifts the lock for its own members.

Who approves a Team Bot in Microsoft Teams?

A Microsoft Teams admin, under Teams apps, Manage apps, Pending approval in the Teams admin center. A Cursor team admin must enable Microsoft Teams first.

Where do I see what Bots actually did?

Turn on Action Recording and export the events through OpenTelemetry. Audit logs cover admin and control-plane events, not each Bot action.

Can Team Secrets be read by a Bot?

No. Team Secrets only reach your Team Setup scripts as environment variables, and the value is gone once the script finishes unless the script saved it.

📺 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

Start with step one today, get your plan checked on a free SEO strategy session, learn the setups in the AI Profit Boardroom, and roll out Grok Bot Enterprise one pilot group at a time.

§ Field reports

Real wins from inside the AI Profit Boardroom

See all 3,400+ members →
AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot AIPB member win screenshot

Scroll sideways →

⚑ Next step

Ready to run AI agents that actually do the work?

Join 3,400+ operators inside the AI Profit Boardroom. Get 1,000+ plug-and-play AI agent workflows, 5 coaching calls a week, and a community that holds you accountable.

Join The AI Agent Community →

7-day no-questions refund · Cancel anytime

Found this useful? Get more of this site in your Google.

One tap adds us as a preferred source — Google then shows you our posts more often in Search, Top Stories, and AI Overviews.

← Back to all posts