Grok Bot Enterprise is Grok Bot set up for organizations: shared AI workers called Team Bots that do multi-step jobs on cloud computers, plus an admin layer for access, networks, approvals and audit that a company can govern centrally.
This page lays out every feature the docs describe, splits them between the Team and Enterprise plans in one table, and says which kind of company each plan suits.
xAI introduced it in its Grok Bot for Enterprise post on 3 September 2026, and the admin reference lives in Grok Bot for teams and enterprises.
Sharing rules come from Team Bots, hosting answers from Grok Bot security, and the newest additions from the v1.0.1 changelog of 11 November 2026.
Choosing tools for your own team? Book a free SEO strategy session and my team will talk it through with you.
What Grok Bot Enterprise actually is
Start with the product itself.
A Bot is a worker you create for one job, and the launch post says each one runs on its own computer in the cloud and can use apps and websites the way a person does.
You message it like a colleague, it works on its own, and it checks back when it needs a decision.
The enterprise layer sits on top: an organization decides who gets Bots, what they can reach, which actions need a human, and what gets logged.
Admins do that on the Grok Bot page of the Cursor dashboard, which members never see.
The core features, one by one
Autonomous cloud workers
Each user's work runs in a dedicated Firecracker microVM, a small virtual machine with hardware separation from other users.
A Bot has no access by default and only uses the accounts and apps it's given.
All of one person's Bots share that person's computer.
Workflow learning
The skills and routines page describes Teach a task: open the Bot's computer view, demonstrate a browser workflow once, and review the skill it drafts.
Recording covers visible screen activity for up to ten minutes and skips microphone audio.
The docs treat that learned skill as a draft you refine with decision rules and approval limits.
Team Bots and collaboration
A Team Bot is shared like a document, with the team, the organization or named people and groups, and no copy is made.
Every person's chat with it is private, the owner's included.
Since 11 November 2026, anything a teammate teaches it for the team waits under Review learnings until the owner or a Manager approves.
Integrations
The overview page lists Slack, Notion, Drive and Teams among the everyday tools, and adds that custom tooling lets a Bot talk to any MCP server or API.
Team Bots can also be added to Slack channels and, since v1.0.1, to Microsoft Teams.
Meetings
On Team, Enterprise and Ultra plans, a Bot can attend a Google Meet, Zoom or Microsoft Teams call from a pasted link, reply in the call chat and post a summary after.
Admin controls, grouped the way the docs group them
- Access and identity: the company-wide enable switch with group access, SCIM provisioning, the team icon.
- Agent capabilities: Cloud Agent delegation, public template sharing, Bot sharing, Allow Shared Logins, Slack Workspace Access, Manage Bots, Microsoft Teams, Meetings, Page sharing, Agent Email, connector policy, local execution, local egress routing.
- Rules and approvals: Team Rules, Enforce Auto-review, team Auto-review rules, inference hooks.
- Computers and network: Network Controls, Team Setup Scripts, Team Secrets, sudo, bulk recreate or delete of member computers.
- Logging and audit: Action Recording, audit logs, OpenTelemetry export, data retention periods.
- Group settings: widen any of the above for one cohort, network policy aside.
The admin reference marks every Enterprise-only item, which is what the next table is built from.
Team vs Enterprise, side by side
| Area | Team plan includes | Enterprise plan adds | Best for |
|---|---|---|---|
| Turning it on | On for every member automatically, no off switch | Admin enable switch, Manage Group Access, Admin API enable | Enterprise: phased rollouts by group |
| People and sign-in | Members sign in with their Cursor accounts | SCIM 2.0 provisioning and deprovisioning | Enterprise: frequent joiners and leavers |
| Team Bots | Create, share, Review learnings, shared connectors | Same, plus group-level settings | Both |
| Channels | Slack and Microsoft Teams connections | Same | Both |
| Meetings | Google Meet, Zoom, Microsoft Teams calls | Meetings switch for everyone's Bots | Both |
| Approvals | Members' own Auto-review | Enforce Auto-review, team Ask first and Allow rules | Enterprise: regulated or client-facing work |
| Network | No team network policy | Allowlists, blocked sites, Apply to MCP servers | Enterprise: strict data boundaries |
| Computers | Standard hosted computers | Setup scripts, Team Secrets, sudo switch, bulk management | Enterprise: company tooling on every computer |
| Model requests | No model control | Inference hooks (beta) | Enterprise: security teams screening prompts |
| Audit | No audit log | Audit logs, Action Recording, OpenTelemetry export | Enterprise: security reviews |
| Data lifecycle | No retention settings | Retention periods for Bots, computers, messages | Enterprise: data-retention policies |
For current plan terms, check the plan matrix the docs link to.
Individuals can still get Grok Bot alone, and The X Subscription includes it on Premium, Super and Ultra but not Plus, per the subscription page.
๐ฅ Want to see these admin settings set up 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 how they set up Bots for their teams. โ Join the AI Profit Boardroom
What the 11 November 2026 update added for teams
- Bots on Team, Enterprise and Ultra plans can attend Google Meet, Zoom and Microsoft Teams calls.
- Team Bots can be brought into Microsoft Teams after three separate approvals: the Cursor team admin, the Bot's owner or a Manager, and a Microsoft Teams admin.
- Owners and Managers can lend their own app login to a Bot as a shared connector, once an admin allows it.
- Team learnings now queue for approval instead of saving instantly.
- Admins can restrict Bot sharing to admins only.
- Comments teammates leave on a Team Bot's Pages now reach the Bot, and custom MCP connectors added to a Team Bot are now labelled as shared with all its users.
Every item is from the v1.0.1 entry in the changelog, and none of them changes which tier you need for the Enterprise-only controls.
Questions to settle before you buy
- Does anyone outside your team need to be added and removed automatically? That points to SCIM and Enterprise.
- Will a security reviewer ask for logs of Bot actions? Action Recording and audit logs are Enterprise only.
- Must Bots be kept off certain websites? Network Controls sit on Enterprise.
- Should a few approval rules be impossible for staff to switch off? That's Enforce Auto-review, also Enterprise.
- Is US-only cloud hosting acceptable to your clients? Both tiers depend on it.
- Do most of your people work in Slack or Microsoft Teams? Both tiers connect to each.
Answer yes to any of the first four and Enterprise is the tier to ask about; answer no to all four and Team covers you.
Who the Team plan suits
- Small and mid-size teams that want shared Bots in Slack or Microsoft Teams without an IT project.
- Agencies and service firms that need one reporting or notes Bot used by several staff.
- Teams whose clients don't send security questionnaires about AI tools.
- Owners happy to set a few sharing switches and leave approvals to each member.
Who the Enterprise plan suits
- Companies that provision staff through Okta or Entra ID and want SCIM to add and remove people.
- Teams that must restrict which sites Bots can reach and route private traffic through their own network client.
- Organizations whose security team wants every model request screened and every Bot action exported.
- Firms with retention policies that require old messages and idle computers to be deleted on a schedule.
- Rollouts that should start with one group and widen over time.
What neither plan offers today
These limits apply to both tiers, and they're where buyers most often get caught out.
Grok Bot runs only on hosted cloud computers; on-premises, inside-your-perimeter and bring-your-own-image deployment aren't supported today.
Computers run in the United States, with a US-only residency program you join through your account team.
Egress uses shared static IPs, and per-customer IPs aren't offered.
Grok Bot manages its own model selection, and the team model allowlist doesn't govern it.
On the certification side, the docs name ISO/IEC 27001 and ISO/IEC 42001 held by Anysphere, the company behind Cursor, with Grok Bot in scope.
Common mistakes when choosing a plan
- Assuming Team has an off switch. It doesn't; every member gets access straight away.
- Relying on blocked-site lists. The docs call blocking best-effort and say it isn't a security boundary. Use an allowlist mode where it matters.
- Skipping Enforce Auto-review. It's off by default, so team rules don't bind members until you turn it on.
- Turning on Allow Shared Logins casually. Every user of that Bot then acts as the Manager whose account is shared.
- Forgetting the Teams admin. Microsoft Teams needs a Microsoft Teams admin to approve each Bot, and Microsoft doesn't notify them. See our Grok Bot Microsoft Teams guide.
- Leaving Privacy Mode (Legacy) on. It blocks Grok Bot entirely.
๐ Want a second opinion before you choose? Book a free SEO strategy session and my team will compare the two plans against your own setup with you. โ Book your free strategy session
How a rollout looks on each plan
On Team, the rollout is mostly about Bots: audit the connector policy, set Bot sharing and Allow Shared Logins, publish one Team Bot, connect Slack or Microsoft Teams, and let people use it.
On Enterprise, the order flips: enable for one group, wire SCIM, set Network Controls, turn on Enforce Auto-review, add team Ask first rules, install tooling with setup scripts, then publish Bots and switch on Action Recording.
Either way, start the first Bot on a read-only job and keep sending, spending and deleting behind approval cards.
For calls, our Grok Bot meeting guide shows the join flow.
Bottom line: which plan to pick
Pick Team when collaboration is the goal: shared Bots, private chats, chat-tool connections, meeting notes and approved learnings.
Pick Enterprise when governance is the goal: provisioning, network boundaries, locked approval rules, screened model requests and logs.
Rule out both, for now, if your policy needs on-premises hosting, dedicated IPs, a fixed model list or data outside the United States.
Setup trainings for both tiers are inside the AI Profit Boardroom.
Also On Our Network
- ๐ What the business edition is, plus the ten admin moves to roll it out
- ๐ What a small business actually gets from the business plans, with three use cases
- ๐ What the business edition is, with three Agent OS prompts to roll it out
- ๐ The business edition feature by feature, with a short note on models
- ๐ The complete Grok Bot Enterprise guide on AI Profit Boardroom
FAQ: Grok Bot Enterprise
What is Grok Bot Enterprise?
It's Grok Bot for organizations: shared Team Bots that work on their own cloud computers, plus admin controls for access, networks, approvals and audit. xAI announced it on 3 September 2026.
What does Enterprise include that Team doesn't?
The company-wide enable switch, SCIM, Network Controls, setup scripts and Team Secrets, Enforce Auto-review and team rules, inference hooks, audit logs, Action Recording, retention periods and group settings.
Do Team Bots work on both plans?
Yes. Team Bots, Review learnings, shared connectors, Slack and Microsoft Teams connections and meetings are all available on the Team plan as well.
Which apps can a Grok Bot work with?
The docs name Slack, Notion, Drive and Teams as examples, and say custom tooling can connect through any MCP server or API.
Can it run in our own data center?
No. The security page says on-premises, inside-your-perimeter and bring-your-own-image deployment aren't supported today.
What security certifications are listed?
ISO/IEC 27001 and ISO/IEC 42001, held by Anysphere and issued by Schellman, with Grok Bot in the current ISO scope.
๐บ 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
Map your needs against the table above, talk them over on a free SEO strategy session, watch the setups inside the AI Profit Boardroom, and choose the Grok Bot Enterprise tier that matches the controls you need.











