⭐ Get the Agent OS + join 3,400+ founders inside the AI Profit Boardroom → Join AIPB

GoldieBench Blog · 6 min read

Grok Bot Enterprise Explained: What It Is, The Features, Team Bots, Team vs Enterprise Controls, And What Benchmarks Can Tell You

The business edition of Grok Bot, feature by feature, with a short closing note on where benchmark scores fit.

Illustrated row of small bot workers at glowing desks linked to an admin control panel, with a faint leaderboard in the background, gold on dark navy

Grok Bot Enterprise is the company edition of Grok Bot, launched by xAI on 3 September 2026: autonomous Bots that each work on a cloud computer, Team Bots that a whole staff can share, and admin controls covering access, networks, approvals and audit.

This guide walks through the feature set first, then the admin layer, and ends with a short note on what the GoldieBench leaderboard can and can't tell you here.

Sources: xAI's launch post, the teams and enterprises docs, the Team Bots page and the Grok Bot changelog.

Planning a rollout? Book a free SEO strategy session with my team.

What the enterprise edition is for

Grok Bot on its own is a personal AI worker.

The enterprise edition is about running many of them across a company without losing track of what they touch.

xAI's announcement framed the release around exactly that: access, network and audit controls so organizations can govern Bots at scale.

The launch post says the heaviest use is outside engineering, and gives sales, recruiting, marketing, finance and engineering examples.

Autonomous workers on their own computers

  • Every user gets a dedicated Firecracker microVM with its own kernel and memory, so one user can't reach another's computer.
  • Within one user, all their Bots share that computer, so a login there is open to each of them.
  • A Bot starts with no access and acts only through accounts and apps it's signed into.
  • Logins come from Vault, a connected password manager or a secure form, and single sign-on or passkey steps are handed to the person.

Workflow learning and skills

Bots pick up routines in two ways.

You can describe a job in writing, or, where it's switched on, use Teach a task: perform the browser workflow once while the Bot records up to ten minutes of screen activity, then review the skill it writes.

The skills and routines docs call that skill a draft and suggest adding decision rules and approval limits before you schedule it.

Team Bots: shared colleagues with private chats

A Team Bot is one Bot used by many people.

Owners share it with the team, the organization or chosen people; Collaborators chat, Managers change it.

Nobody reads anyone else's chat with it, owner included.

Two v1.0.1 additions matter here: learnings from teammates queue under Review learnings for approval, and Managers can offer their own login as a shared connector once an admin enables Allow Shared Logins.

Integrations, meetings and Microsoft Teams

The overview page names Slack, Notion, Drive and Teams as the tools Bots work best with, and notes that Bots can also use custom tooling over MCP or an API.

Team Bots can be added to Slack, and since 11 November 2026 to Microsoft Teams, after a Microsoft Teams admin approves them; our Grok Bot Microsoft Teams guide has the steps.

Bots on Team, Enterprise and Ultra plans can also join Google Meet, Zoom and Microsoft Teams calls and send a summary afterward, covered in the Grok Bot meeting walkthrough.

The admin layer: Team vs Enterprise

ControlTeamEnterprise
Grok Bot on for membersAlways, by defaultAdmin enables, by group
Team Rules, Bot sharing, Allow Shared LoginsYesYes
Microsoft Teams and Meetings switchesYesYes
SCIM provisioningNoYes
Network Controls and blocked sitesNoYes
Enforce Auto-review and team rulesNoYes
Setup scripts plus the secrets they readNoYes
Model-request screening via hooks, in betaNoYes
Audit trail and exported Bot actionsNoYes
Retention periods, group settingsNoYes

The docs mark each Enterprise-only control individually, and say the access table and the control list are separate things.

For current plan terms, use the plan matrix the docs link to.

Hosting and data facts buyers ask about

  • Computers run in the United States; a US-only residency program is available through the account team.
  • On-premises and bring-your-own-image deployment aren't supported today, per the security page.
  • With Privacy Mode on, customer data isn't used for training.
  • Grok Bot falls inside the ISO/IEC 27001 and 42001 certification scope held by Anysphere, maker of Cursor.

How companies usually roll it out

  1. Clear the blockers: leave Privacy Mode (Legacy) and exempt Cursor's domains from any inspecting proxy.
  2. On Enterprise, enable Grok Bot for one pilot group with Manage Group Access.
  3. Set Network Controls to an allowlist mode and turn on Enforce Auto-review, then add team Ask first rules for outside email, payments, live changes and legal terms.
  4. Set Execution on Local Computer to Never allow and Bot sharing to Admins only while you learn.
  5. Publish one Team Bot on a read-only job and connect it to Slack or Microsoft Teams.
  6. Switch on Action Recording and export it to your collector, then widen access group by group.

On the Team plan, skip the Enterprise-only steps; the Bot, sharing and channel steps still apply.

Who should start on Team, and who needs Enterprise

Small firms that mainly want one shared notes or reporting Bot in their chat tool can start on Team and lose nothing they'd use.

Companies with an identity provider, a security reviewer, website restrictions or retention rules will hit Enterprise-only switches within the first week.

Teams in between can pilot on Team and move up when the first client or auditor asks for logs.

A short note on models and GoldieBench

One thing admins can't set is the model: the docs say model choice is made by Grok Bot itself, and a team's model allowlist has no effect on it.

Enterprise teams can screen model requests with inference hooks instead, starting in Shadow mode, which logs denials without blocking.

So no row on the GoldieBench leaderboard scores a Grok Bot reply, the one named Grok included.

Where the bench helps is the files Team Bots share, such as Pages and internal tools. Its methodology scores one-shot, single-file builds 0 to 10.

ModelPages avgSims avgOverall
Fusion8.508.508.59
Claude Opus 58.478.638.27
GPT-5.6 Sol8.478.338.16
Qwen 3.88.408.588.10
Grok8.337.968.09

Scores read live on 15 November 2026. Pages has only three tasks, so use it to shortlist a template model, not to rank Grok Bot.

My verdict on Grok Bot Enterprise

It's a strong shared-worker product with an unusually detailed admin layer.

The features that stand out are the per-person cloud computers, Teach a task, Team Bots with approved learnings, and the chat-tool and meeting connections added in November.

The gaps are structural: cloud-only US hosting, shared egress addresses and no say over the model.

Team covers collaboration; Enterprise adds the provisioning, network, approval and audit controls a security team will ask for.

Learn the setups inside the AI Profit Boardroom before you widen it past a pilot group.

Also On Our Network

Start with one pilot group, get your plan checked on a free SEO strategy session, and learn the builds in the AI Profit Boardroom so your team gets the most from Grok Bot Enterprise.

FAQ

What does Grok Bot Enterprise include?

Autonomous Bots on cloud computers, shared Team Bots, workflow learning, app integrations, meetings, and admin controls for access, networks, approvals and audit.

When was it launched?

xAI's Grok Bot for Enterprise post is dated 3 September 2026.

Is the Grok row on GoldieBench a Grok Bot score?

No. It scores one-shot single-file builds from a model called Grok. Grok Bot picks its own model for each request.

Which features are Enterprise only?

Provisioning with SCIM, network allowlists, setup scripts with their secrets, locked Auto-review, model-request screening, logging and export, retention and per-group settings.

Can admins choose the model?

No. Grok Bot manages model selection; Enterprise teams can use inference hooks to allow or deny each governed request.

Is our data used for training?

With Privacy Mode on, the docs say customer data is not used for training.

The same stack Julian uses

Run this stack yourself.

Every demo on this bench was built inside the Agent Operating System — one prompt, one shot, single HTML file out. The Agent OS, the prompts, the templates, the weekly walkthroughs and 3,400+ founders shipping with it every day all live inside the AI Profit Boardroom.

3,400+founders
258documented wins
38countries
4coaching calls a week