Configure Auto Review team instructions and Team Rules for Grok Bot

Team admins shape what every member’s Bots may do with two dashboard controls: Team Rules (always-on guidance) and Auto Review team instructions (allow/block lines the independent review model applies before risky actions run). Official guides: Grok Bot for teams and enterprises → Admin controls; Grok Bot security → Approvals and Auto Review; Approvals, security, and privacy.

Both controls are available on Teams and Enterprise. They sit in different places.

Control	Where	Role
Team Rules	Grok Bot page of the Cursor dashboard	Short required rules for every member’s Bots
Auto Review team instructions	Team Settings → Security and Automation	Team-wide allow and block instructions for the reviewer
Member Auto-review rules	Settings → General → Auto-review (desktop)	Personal Require Approval / Always Allow rules

Team Rules

1. Sign in as a team admin and open Grok Bot in the Cursor dashboard.
2. Open Team Rules.
3. Add short, few rules (example: never move company data to personal accounts).
4. Scope each rule to Cursor, Grok Bot, or both.
5. Save. Rules are always required — they cannot be marked optional.

Use Team Rules for standing guidance. For hard stops on specific action classes, add Auto Review team instructions.

Auto Review team instructions

Auto Review is an independent review model that evaluates risky Bot actions before they run: shell commands, plugin calls, computer use, automation writes (routines and event triggers), and delegation (Cloud Agent and subagent launches). It can let an action proceed, require approval, or deny it.

Enforcement is enabled by Cursor and is currently active for all users. Each member’s own Auto Review setting remains the off switch; an organization-level lock is not available. For security-sensitive deployments, ask members to leave it on.

1. Open Team Settings → Security and Automation (not the Grok Bot page).
2. Add block instructions for actions that are never acceptable (common examples: production deployments, external email, payments, accepting legal terms).
3. Add allow instructions for routine safe work your org wants to reduce friction on.
4. Keep instructions narrow and scoped to a known action class.

Team instructions apply for every member. Members can still add personal rules under Settings → General → Auto-review:

• Require Approval — always stops matching actions for that member.
• Always Allow — lets matching actions proceed only when the review finds no other reason to stop.
• When both match, Require Approval wins.

Personal rules are stored on the current desktop and synced to its Grok Bot computer; another desktop install needs its own. Prefer narrow personal rules (require approval before sending any external email, always allow running git status in /workspace/reports) over broad ones like “allow everything in the browser.”

How approvals still work

Even with team instructions in place, consequential actions show a proposed operation and inputs in the conversation. On desktop: Allow once, Always allow, or Deny. On iPhone and Android: Approve once or Deny. An approval covers the proposed action only — it does not undo work already completed. Do not approve an action whose target or effect you cannot identify.

Ask members to put boundaries in the request itself (what the Bot may change and where it must stop). Auto Review complements per-action approvals, Network Controls, and per-user isolation; it does not review every side effect (memory writes and most settings changes are examples).

Recommended admin baseline (security-sensitive)

From the teams-and-enterprises recommended configuration:

1. Configure Network Controls (Enterprise) so teams do not stay on allow-all by accident.
2. Audit connector policy before broad enablement.
3. Ask members to keep Auto Review enforcement on.
4. Set an explicit local-execution policy.
5. Disable Cloud Agent spawning if you do not need delegation.
6. Keep public template sharing off unless members should publish templates outside the team.
7. Add team block instructions for production deploys, external email, payments, and accepting legal terms; allow instructions for routine safe work.
8. Gate Grok Bot sign-in to managed devices through your IdP (device-aware SSO on the member device).

Pitfalls

• Looking for Auto Review team instructions on the Grok Bot page — they live under Team Settings → Security and Automation.
• Relying on Team Rules alone for enforcement — use Auto Review block instructions for hard stops.
• Broad Always Allow rules that cover whole browsers or whole workspaces.
• Assuming an org-level lock exists for Auto Review — members can still turn personal enforcement off.