Turning Grok Bot on for a team takes about a day. Deciding who gets it and what you can trace later is the slow part, and it is hard to add after people are already using it. This post covers only what admins should settle before clicking Enable in the Cursor enterprise dashboard, based on the official Teams, Enterprise, and security docs.
Six decisions first
- Who gets it. Everyone, or specific groups. Enterprise has Manage Group Access for this.
- Privacy mode. Privacy Mode (Legacy) blocks Grok Bot for the whole workspace, so you have to move off it first.
- Approvals. Turn on Enforce Auto-review, then add team Ask first rules for outbound email, payments, production deploys, and accepting legal terms.
- Network. Configure Network Controls. With no policy, all traffic is allowed.
- Local execution. Set Execution on Local Computer to Never allow unless the Bot really needs members' own machines.
- Audit scope. The Audit Log covers the control plane. Action Recording covers tool actions. Action Recording is off by default and its events do not show on the Audit Log page.
Also review connectors in the Teams Marketplace. A connector you allow is available to every Bot a member owns.
Teams or Enterprise
| Teams | Enterprise | |
|---|---|---|
| Default | On for every member | Admin enables it |
| Org-wide off switch | No | Yes (blocks members, keeps their computers) |
| Per-group access | No | Manage Group Access |
| Network Controls, Enforce Auto-review, Action Recording, Audit Log | Not in self-serve Teams | Yes |
On self-serve Teams, a member can use Grok Bot as soon as they join, and there is no switch to hold it back company-wide. Organization-level enablement, groups, network policy, and enforced approvals require Enterprise.
A Bot acts as the member
Per the security docs, a Bot has no identity or credentials of its own. It acts as the signed-in member, never with more permission than that member, and every action maps to a person. Connector OAuth tokens stay in Cursor's backend; the Bot never sees the plaintext token.
Sign-ins, 2FA, and payment confirmations go back to the member. To revoke access, remove the member from the team or turn Grok Bot off for their group, then revoke their sessions in your identity provider. Terminating the cloud computer alone does not revoke access.
The official hardening baseline
For deployments with strict security needs, the docs ask admins to at least:
- configure Network Controls
- review connector policy before enabling
- turn on Enforce Auto-review and set team Auto-review rules
- set Execution on Local Computer to Never allow when there is no local need
- turn off Cloud Agent if you don't need delegated coding
- keep public template sharing off
- cover production deploys, outbound email, payments, and legal terms with Ask first rules
Members should keep credentials out of ordinary chats, pick Allow once for anything touching accounts, money, or shared resources, and sign out of sites they no longer need when a task ends. Multiple Bots under one user share one cloud computer, so files and sign-in state can be visible across Bots.
Which log answers which question
Audit Log (Enterprise) records admin, security, and auth events plus Grok Bot control-plane changes, for example:
-
sand_onboarding(enable/disable) grok_bot_createdgrok_bot_access_changedmcp_authenticationgrok_bot_routine
You can filter by application in the dashboard. Streamed events carry application_type, which is grok_bot for Grok Bot, so they can go to a SIEM.
Action Recording (Enterprise, off by default) records the tool actions a Bot took: redacted shell commands, connector calls, browser navigation metadata, routine runs. These do not appear on the Audit Log page. Export them with OpenTelemetry; events carry cursor.surface=grok_bot. The docs state 90-day internal retention. Privacy Mode (Legacy) forces it off.
Rule of thumb:
- "Who changed permissions, created a Bot, or connected an MCP server?" Check the Audit Log.
- "Which tools did the Bot call in this task?" Turn on Action Recording and export over OpenTelemetry.
After enabling, check three things
- Which accounts or groups have Grok Bot.
- Whether Enforce Auto-review and Ask first rules cover outbound sends, payments, and deploys.
- Whether the Audit Log can be filtered by
grok_bot, whether it streams to your SIEM, and whether you also need Action Recording.
Originally published at fxai.ai.
Top comments (0)