Repository Public
1<!-- source: https://docs.x.ai/grok-bot/teams-and-enterprises (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Grok Bot for teams and enterprises56Grok Bot gives each person on your team standing Bots for everyday work:7research, operations, documents, browsing, and automations. This page is for8team and organization admins rolling Grok Bot out. Security reviewers should9start with [Grok Bot security](/grok-bot/security) and the10[Grok Bot security FAQ](/grok-bot/security-faq). Members who want the approval11model should start there too.1213## Availability1415| Plan | Access |16| --- | --- |17| Individuals | Included with every paid Cursor plan, or through an individual SuperGrok link |18| Teams | Included; every member has access, and usage follows the seat's allowance |19| Enterprise | Enable Grok Bot for your team from your dashboard |2021That table is product access, not the admin control list. Grok Bot is included22on Teams. Several settings are Enterprise only and do not appear for23self-serve Teams. [Admin controls](#admin-controls) marks each one.2425[Plans and billing](https://cursor.com/help/grok-bot/plans) is the canonical26plan and usage matrix.2728## Enabling Grok Bot for your team2930On the Teams plan, Grok Bot is enabled by default, and every member has access31without any admin action. It stays off for teams on Privacy Mode (Legacy) or on32a [legacy request-based plan](https://cursor.com/docs/models-and-pricing#legacy-request-based-pricing).33There is no switch to turn it off.3435On the Enterprise plan, an admin turns it on from36[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). Once37enabled, you can give access to all team members or limit it to specific38groups with **Manage Group Access**. Turning Grok Bot off blocks every member39without deleting their computers.4041Admins on either plan can bring members in with **Invite Team** on the Grok Bot42page. Existing Cursor users on your team get an email with a download link. New43users get an invitation to your Cursor team, by email or invite link, that also44points them to Grok Bot. Teams that manage membership through SCIM see only the45existing-users option.4647## Before you roll out4849* Move off Privacy Mode (Legacy). That setting blocks Grok Bot entirely, and50 you are prompted to change it before enabling. Check the privacy setting in51 Team Settings.52* Plan for shared egress addresses. If your company restricts services by53 source IP, see [static egress IPs](/grok-bot/security#static-egress-ips).54* Clear your gateway. If member devices sit behind Zscaler or another55 TLS-inspecting proxy, allow Cursor's domains, including the nested56 `*.*.cursorvm.com` pattern, and exempt them from inspection before members57 connect. See58 [Configure TLS-inspecting proxies](/grok-bot/proxies).59* Decide how members sign in to company tools from the computer. See60 [identity and sign-ins](/grok-bot/security#identity-and-sign-ins).61* Review the policies Grok Bot inherits: Team Rules and the connector policy on62 every plan, plus team Auto-review rules and the MCP allowlist on Enterprise.6364## Architecture6566### How Grok Bot is built6768Grok Bot is a computer-use agent that operates applications, browsers, and69development environments. It runs in Cursor's cloud, and each user's work70executes on a dedicated cloud computer. The desktop and mobile apps are thin71clients for chat, review, and approvals.7273The security model rests on four principles:7475* Per-user isolation. Each user's work runs in a dedicated Firecracker microVM,76 a micro virtual machine with hardware-level separation from other users.77* No access by default. A Bot can use only the accounts and plugins the user or78 team grants it.79* Human approval gates. Sensitive actions require user approval, evaluated by80 an independent review model called Auto Review.81* Administrative control. Team admins can set Team Rules, Cloud Agent82 delegation, template sharing, and the local execution ceiling. Network83 Controls, Team Setup, Allow Local Egress, Action Recording, Enforce84 Auto-review, Auto-review rules, and the organization-wide enable switch are85 Enterprise only.8687The pieces fit together like this:88891. Local machine. Chat, review, and approvals happen on the member's device.90 Work runs in the hosted computer. Optional91 [local execution](/grok-bot/security#local-execution) requires per-command92 approval by default and can be turned off.932. Environment. One persistent Firecracker microVM per user. Every Bot that94 user runs shares that computer. Admins manage Grok Bot from the Grok Bot95 page of the [Cursor dashboard](https://cursor.com/dashboard/bot). Team96 Rules, Cloud Agent delegation, public template sharing, and Execution on97 Local Computer are available to team admins. Enterprise only on that page:98 the organization-wide enable switch, Network Controls, Team Setup, Allow99 Local Egress, Action Recording, Enforce Auto-review, Auto-review rules, and100 computer management for organization admins. Members never see this page.1013. The Bot. Shell, browser, and computer use inside the hosted computer. A Bot102 has no access by default and acts only with accounts the member signs it103 into. It hands login, two-factor authentication, and payment steps to the104 member.1054. Plugins. Your team's Cursor MCP (Model Context Protocol) policy applies in106 full, allowing or blocking each connector. OAuth tokens stay on Cursor's107 connector backend, and Bots invoke tools without receiving them.1085. Cloud Agents. Grok Bot can delegate coding tasks to separate computers under109 your existing [Cloud Agent](https://cursor.com/docs/cloud-agent) controls.110 Admins can disable spawning.1116. Models and data. Cursor manages model selection. With Privacy Mode enabled,112 customer data is not used for training; Cursor enforces this on its servers,113 and when the setting cannot be verified, the system defaults to not training.114115### How users are isolated116117Each user gets a dedicated computer with hardware-level separation, and one118user cannot reach another user's computer. Every computer is a Firecracker119microVM with its own kernel, memory, and virtual devices.120121Within one user, the boundary is different: all of that user's Bots share one122computer, and Bots isolate personalities and workspaces, not compute. Treat a123login or file on the computer as available to every Bot that user runs, sign124the browser out of accounts a Bot no longer needs, and remove sensitive125temporary files when work completes. When a workload needs its own computer and126credential set, give it its own Cursor user.127128## Admin controls129130Most Grok Bot settings sit on the Grok Bot page of the131[Cursor dashboard](https://cursor.com/dashboard/bot), which only admins see. A132few live in Team Settings, your Team Marketplace, or your identity provider.133Several controls are available only on the Enterprise plan; the rest are134available on Teams and Enterprise.135136### Access and identity137138Who can use Grok Bot, and how members are provisioned.139140#### Enable Grok Bot141142The organization-wide switch on the Grok Bot page, labeled **Enable Grok Bot143for your team**, with **Manage Group Access** beside it. A team that has never144set up Grok Bot sees a **Set Up Grok Bot** call to action with an **Open Docs**145link instead; on Enterprise it opens a setup modal that covers privacy mode,146pricing, and model availability. Turning the switch off opens a **Disable Grok147Bot** confirmation and then blocks every member without deleting their148computers. On the Teams plan the same card is a status line, **Grok Bot is149enabled for your team**, with no switch. See150[Enabling Grok Bot for your team](#enabling-grok-bot-for-your-team).151152Available on the Enterprise plan.153154#### SCIM155156SCIM 2.0 provisioning and deprovisioning through your identity provider.157Members sign in to Grok Bot with their Cursor account, so your existing158[SCIM](https://cursor.com/docs/account/teams/scim) and SSO setup carries over.159For Okta and Entra ID steps, including app assignment and sign-in rules for the160computer browser, see161[Configure identity and access](/grok-bot/identity-and-access).162163Available on the Enterprise plan.164165### Agent capabilities166167What Bots may do on behalf of members. Each control applies to every member's168Bots.169170#### Cloud Agents171172Allows or blocks Bots delegating coding tasks to Cursor Cloud Agents. The173switch is on the Grok Bot page, applies to the whole team, and is on by174default. Delegated work runs on separate computers under your existing175[Cloud Agent](https://cursor.com/docs/cloud-agent) controls. Turn it off when176your team does not need delegation.177178#### Public template sharing179180Controls whether members can publish Bot templates outside your team. Off181keeps sharing team-only, and Cursor enforces the policy on its servers,182including for templates that are already public. Enterprise teams start with183public sharing off; other teams start with it allowed. For what a shared184template contains, see [Share a Bot](/grok-bot/bots#share-a-bot).185186#### Connector policy187188Grok Bot inherits your team's Cursor connector policy. There is no separate189Grok Bot connector list, and connectors appear as plugins in the app. Set which190servers members can use from your Team Marketplace on the dashboard's191[Plugins page](https://cursor.com/dashboard/plugins), not on the Grok Bot page.192The MCP allowlist is Enterprise only; see193[MCP server trust management](https://cursor.com/docs/enterprise/model-and-integration-management#mcp-server-trust-management).194Any permitted connector is available to every Bot a member runs, and a blocked195one shows as **Disabled by team admin**. Pushing connectors to members, whether196mandatory or default-on, is not available.197198#### Execution on Local Computer199200Caps what Bots may do on a member's own machine through the desktop app: open201files and run tasks. Pick **Always allow**, **Ask every time**, or **Never202allow** on the Grok Bot page. **Always allow**, the default, leaves the choice203to each member, whose own setting defaults to asking before every task. **Ask204every time** makes every local task ask for approval, and **Never allow** turns205local execution off for the whole team. A member's own setting still applies206when it is stricter than the team's. Pick **Never allow** unless Bots have a207specific reason to work on member machines. See208[local execution](/grok-bot/security#local-execution).209210#### Allow Local Egress211212Let members route Grok Bot's web traffic through their own computer. Off213disables the option in Grok Bot. The switch is on by default. Turning it off214stops active routes within five minutes. Turning it back on restores each215member's previous choice. See216[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).217218Available on the Enterprise plan.219220### Rules and approvals221222Guidance Bots follow, and the review layer that stops actions.223224#### Team Rules225226Rules that every member's Bots follow. Add them from the Grok Bot page and227scope each rule to Cursor, Grok Bot, or both. Rules applied to Grok Bot are228always required, so members cannot turn them off. Keep them short and few, like229"never move company data to personal accounts." Rules guide a Bot; for approval230behavior, use [Auto-review rules](#auto-review-rules).231232#### Enforce Auto-review233234Prevents members from turning Auto-review off. The switch is on the Grok Bot235page and is off by default. When it is on, Bots always check risky actions236before running them and ask for approval when needed. Turn it on before you237rely on team Auto-review rules.238239Available on the Enterprise plan.240241#### Auto-review rules242243Team-wide **Ask first** and **Allow automatically** rules that apply to every244member's Bots on top of their own rules. Add them with **Configure Rules** on245the Grok Bot page; changes save automatically. Members see the team rules under246**Settings → General → Auto-review** but cannot edit or delete them, and **Ask247first** wins when rules conflict. Turning enforcement off stops applying the248team rules. See249[approvals and Auto Review](/grok-bot/security#approvals-and-auto-review).250251Available on the Enterprise plan.252253### Computers and network254255How team computers are set up, what they can reach, and how you recreate or256terminate them.257258#### Network Controls259260Restricts which destinations team computers can reach. On the dashboard the261section is **Network** and the control is **Grok Bot Network Access**. Pick one262of four modes, from allow-all to a team allowlist of domains and IP ranges:263**No Policy (Allow All)**, **Allow All Network Access**, **Defaults + Team264Allowlist**, or **Team Allowlist Only**. Directory groups can carry their own265policy as **Group Network Access**, and **Lock for all groups** makes the team266policy apply to everyone. Teams without a policy default to allow-all. See267[network policy](/grok-bot/security#network-policy) for the modes and how a268new policy reaches running computers.269270Available on the Enterprise plan.271272#### Team Setup273274Manifests of install scripts that run on every team computer, so the same275tooling is present everywhere. Keep secret values out of setup scripts. Members276do not see or manage the setup in the app; scripts run on their computer when277it starts and on a periodic refresh. For how manifests run, and to install a278networking client that reaches private services, see279[Connect to private networks](/grok-bot/private-networks).280281Available on the Enterprise plan.282283#### Grok Bot Computers284285Lets organization admins recreate or terminate the computers of many members286at once, with a result for each member. Team admin rights are not enough,287because one computer spans every team the member belongs to. **Recreate** moves288members to the latest image and Team Setup while keeping their Bots, files, and289logins. **Terminate** ends the member's current work and keeps the durable290disk; the member's next session starts a fresh computer on it. Neither action291removes access: to do that, remove the member from the team or turn off Grok292Bot for their group, and revoke their sessions in your identity provider. See293[Manage Grok Bot computers](/grok-bot/computers).294295Available on the Enterprise plan.296297### Logging and audit298299What gets recorded, and where it goes.300301#### Action Recording302303Records Bot actions: connector (MCP) tool calls, shell commands, browser304navigations, and computer use sessions. Events are sanitized before they are305stored or exported. Shell commands are secret-scrubbed; browser navigations306keep each page as `scheme://host/path` with the title but strip query strings307and credentials; computer use sessions record action and screenshot counts and308the session duration, without the screenshots, clicks, or typed text. The309switch is on the Grok Bot page and is off by default. Recorded events do not310appear on the Audit Log page. To receive them in your own collector, configure311[OpenTelemetry Export](#opentelemetry-export), which delivers each event312tagged `cursor.surface=grok_bot`. Retention details are on313[logging and audit](/grok-bot/security#logging-and-audit).314315Available on the Enterprise plan.316317#### Audit logs318319Admin, security, and authentication events, plus Grok Bot control-plane320events: Bot creation, member access changes, Team Setup manifests, MCP321authentication, Slack account links, and routines. Each row names the322application that acted, so you can filter the log to Grok Bot. View them on the323[Audit Log page](https://cursor.com/dashboard/audit-log) or stream them to324your SIEM; see325[audit logs](https://cursor.com/docs/enterprise/compliance-and-monitoring#audit-logs).326For the actions Bots took, use [Action Recording](#action-recording).327328Available on the Enterprise plan.329330#### OpenTelemetry Export331332Streams Cursor usage metrics and logs, including recorded Grok Bot actions, to333a collector you run. It is the customer path for Action Recording events.334Configure it under **Team Settings → OpenTelemetry Export**. Endpoint335requirements and the event schema are on336[OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export).337338Available on the Enterprise plan.339340## Admin API341342Enable Grok Bot and manage capabilities, Enforce Auto-review, group access,343network policy, team rules, and setup scripts through the344[Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot).345346## Security347348The security model, network policy, approvals and Auto Review, identity,349logging, data handling, and certifications live on350[Grok Bot security](/grok-bot/security). Common review questions are on the351[Grok Bot security FAQ](/grok-bot/security-faq).352353## Recommended configuration354355For security-sensitive deployments, this is the recommended baseline.356357For administrators:3583591. Configure Network Controls. Enterprise only. Teams without a policy default360 to allow-all. Self-serve Teams cannot set this. See361 [network policy](/grok-bot/security#network-policy).3622. Audit connector policy in Teams Marketplace before enabling Grok Bot. Any363 permitted connector is available to every Bot a member runs.3643. Turn on Enforce Auto-review before you rely on team rules. Enterprise only.365 Members can add stricter personal rules on top, and **Ask first** wins when366 rules conflict.3674. Set Execution on Local Computer to **Never allow** unless Bots need to act368 on member machines. The default leaves the choice to each member.3695. Disable Cloud Agent spawning if you do not need delegation.3706. Keep public template sharing off unless members should publish Bot371 templates outside the team.3727. Add team Auto-review rules. Enterprise only. Cover actions that should373 always ask first or can proceed automatically. Production deployments,374 external email, payments, and accepting legal terms are good **Ask first**375 examples. Keep automatic rules narrow.3768. Gate sign-in to managed devices through your identity provider. Grok Bot377 sign-in uses your SSO, so a device-aware sign-in policy applies to it. This378 gates sign-in, not the hosted computer itself.379380For members:3813821. Never paste credentials into chat. The masked secret request is the383 supported path.3842. Prefer **Allow once** over **Always allow** for actions that touch accounts,385 money, or shared resources.3863. Sign the Bot's browser into accounts sized to the task, and sign it out of387 accounts it no longer needs. Use scoped service accounts where the source388 system supports them.3894. Start new roles with read-only tasks and draft outputs, and keep sending,390 publishing, purchasing, deletion, and production changes behind approval.3915. Review installed plugins and active routines regularly, and pause a routine392 when its source system changes.393394## FAQ395396### Can I turn Grok Bot on or off for my team?397398The organization-wide **Enable Grok Bot** switch is Enterprise only. It lives399on the Grok Bot page of the Cursor dashboard. Self-serve Teams do not get this400switch. Disabling blocks members without deleting their computers.401402### Can I manage Grok Bot through the Admin API?403404Yes. Use the405[Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot).406407### Can I set a Grok Bot spend cap?408409A separate Grok Bot spend cap is not available today. Account-level on-demand410controls apply, and the per-product split is on the411[dashboard usage page](https://cursor.com/dashboard/usage).412413### Why does a member see a plugin as Disabled by team admin?414415Your team's connector policy blocks that server. Enable it in Teams416Marketplace, add its server URL to your MCP allowlist if you use one, and have417the member restart the app. If a permitted plugin still fails for regular418members with a vendor-side permission error, check the provider's419requirements; some vendors restrict their MCP endpoints to their own420administrators. See421[Connect an app](/grok-bot/computer-and-apps#connect-an-app).422423### How do members request access?424425Members can send a request from the app. On a pooled Enterprise team whose426admin has not finished setup, members see a team-setup message instead. The427next step is for an admin to use the Enterprise only enable switch. Self-serve428Teams do not use that switch.429430### Can I see what kind of work my team does with Grok Bot?431432Yes, on Enterprise teams where it has rolled out. The Conversation Insights433page of the Analytics dashboard has a Grok Bot source that groups Bot434conversations by Type of Work and Level of Automation. See435[Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights).436437Isolation, egress, approvals, logging, and data-handling questions are on the438[Grok Bot security FAQ](/grok-bot/security-faq).439440## Related pages441442* [Grok Bot security](/grok-bot/security)443* [Grok Bot security FAQ](/grok-bot/security-faq)444* [Configure identity and access](/grok-bot/identity-and-access)445* [Connect to private networks](/grok-bot/private-networks)446* [Configure TLS-inspecting proxies](/grok-bot/proxies)447* [Manage Grok Bot computers](/grok-bot/computers)448* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)449* [Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot)450* [Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights)451* [Plans and billing](https://cursor.com/help/grok-bot/plans)452* [Privacy and Data Governance](https://cursor.com/docs/enterprise/privacy-and-data-governance)453454Contact your Cursor account team about Enterprise plan enablement, egress455ranges, residency commitments, and security review support.456