Grok Bot for teams: what admins actually control

Grok Bot on a team is still a per-person product. Each member gets a dedicated cloud computer. That computer is a managed Linux virtual machine. All of that member’s Bots share it. Files, sign-in sessions, and permissions belong to the member, not to an individual Bot, and not to the whole company.

This page is for people rolling the product out. Individual operators should start with getting started and approvals.

Who currently gets it

Cursor Help currently says:

• Self-serve Cursor Teams (Standard and Premium): every member has access. A Premium seat is not required to turn Grok Bot on.
• Cursor Enterprise: talk to the account team; this is not a self-serve toggle.
• Individuals: paid Cursor individual plans, or a linked individual SuperGrok / Plus / Heavy plan.

xAI’s teams guide also notes a weekly Grok Bot usage allowance on Standard and Premium seats. Confirm current numbers on the official Teams pricing and Grok Bot plan pages; they change.

Enterprise users can join a waitlist. Do not promise coworkers a date this site cannot see.

How sign-in and SSO work

Members use the desktop app on macOS or Windows and the iPhone app. They sign in with their Cursor account, so existing Cursor SSO and team membership apply. If your organization requires SSO, complete that flow; a personal Grok login is the wrong door.

Grok Bot requires cloud data storage. Accounts on Legacy Privacy Mode must move to a supported Cursor data setting before Grok Bot can start.

What to decide before a rollout

1. Privacy mode and data settings. Run the admin setup on the Cursor Grok Bot dashboard. xAI describes a wizard covering privacy mode, the dedicated desktop, API pricing, pooled billing, model availability, and premium seats.
2. Plugin policy. Installed connectors are account-wide for that member. Decide which plugins are allowed, who owns each connection, and whether write/send scopes need a second reviewer.
3. Local-computer access. A Bot can run commands on the member’s laptop only when that capability is enabled and approved. Default off for most roles.
4. Secrets. No passwords, session cookies, private keys, or unrestricted production credentials in prompts. Use the org’s secret manager and computer takeover for 2FA.
5. Customer and regulated data. Write an allowlist. “The Bot is in a VM” is not a processing agreement.

What admins cannot assume

• Separate Bots are not separate security boundaries.
• A member’s computer is not shared with the rest of the team, but anything that member signs into is available to all of that member’s Bots.
• Hiding a Bot does not pause its routines.
• Sharing a Bot profile link is public to anyone who has the link. Strip internal URLs and customer data before anyone copies it.

A minimum team protocol

• Named owner per Bot and per plugin
• Draft-before-send on anything external
• Staging before production
• Weekly usage visible to the member before they launch an overnight job
• Incident step: pause routines, revoke the plugin, keep screenshots, then fix the brief

Sources and verification

Last verified: August 27, 2026.

• Grok Bot for teams and enterprises (xAI)
• Grok Bot plans (Cursor)
• Approvals, security, and privacy (xAI)
• Grok Bot is now included with more plans (xAI)