SPB Git

Repository Public

approvals-security-and-privacy.md 8.0 KB 184 lines markdown

1<!-- source: https://docs.x.ai/grok-bot/approvals-security-and-privacy (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Approvals, security, and privacy56Grok Bot is designed to complete work while keeping sensitive inputs and7consequential actions under your control. Use approvals, secure handoffs, and8clear Bot boundaries together.910## Set a boundary in the request1112Tell the Bot which actions it can take and where it must stop:1314> Reconcile the campaign data and draft a recommended budget change. Do not15> change the campaign or message the agency. Ask for approval after showing the16> current value, proposed value, and expected impact.1718Prefer explicit boundaries for:1920* Sending messages or invitations21* Publishing content22* Purchases and financial transfers23* Deleting or overwriting data24* Changing permissions25* Production changes26* Accepting legal terms2728An approval controls the proposed action. It does not reverse work already29completed.3031## Review an action3233When an action needs approval, the conversation shows the proposed operation34and its inputs. Review the target, scope, and values before approving.3536* On desktop, **Allow once** lets the Bot continue with that action and37  **Deny** blocks it. **Always allow** can save a matching rule.38* On iPhone and Android, the Auto-review sheet offers **Allow**, **Deny**, and,39  when a rule is proposed, **Always allow**; a local-command card offers40  **Allow once** and **Deny**.4142Do not approve an action whose target or effect you cannot identify. Ask the Bot43to explain it in plain language or produce a draft first.4445## Configure Auto Review4647With Auto Review on, Grok Bot evaluates tool calls and computer actions before48they run. Open **Settings → General → Bot → Auto-review** to add rules.4950* **Ask first** rules always stop matching actions for you.51* **Allow automatically** rules let matching actions proceed only when the52  automated review does not identify another reason to stop.53* If both kinds of rule match, **Ask first** wins.5455If your team admin enforces Auto Review, the same table also shows locked team56rules that you cannot edit or delete. Your own rules apply on top and can only57make behavior stricter. See58[Auto-review rules](/grok-bot/teams-and-enterprises#auto-review-rules).5960Write narrow rules around a known action and scope:6162* Ask first before sending any external email.63* Ask first before changing a production dashboard.64* Allow automatically when running `git status` in `/workspace/reports`.6566Avoid broad rules such as “allow everything in the browser.” Websites and tool67behavior change over time. Auto Review is model-based and should complement,68not replace, least privilege and explicit approval boundaries.6970Personal Auto-review rules are saved to your account and applied on every71desktop you sign in to, as well as on your Grok Bot computer.7273## Enter passwords and verification codes yourself7475For passwords, passkeys, two-factor codes, CAPTCHAs, and payment confirmations,76the Bot should hand you control of the computer.77781. Open **Agent Computer**.792. Take control.803. Complete the sensitive step.814. Return control and tell the Bot to continue.8283Do not send a password or one-time code in ordinary chat.8485If the Bot presents a secure secret request for a supported connection, enter86the value in that request. It is not a general-purpose password manager. The87value is masked, excluded from the transcript, and not shown to the model.8889When a web page needs you to type something yourself, such as a login, a90checkout address, or a phone number, the Bot can show a form in the chat, one91form per step, and fill your answers into the page for you.9293If you sign in with a hardware security key, such as a YubiKey, the Bot's94browser can use a key plugged into your desktop while **Use hardware security95keys** is on under **Settings → General → Security Key**. The setting is on by96default on macOS and Windows and is not yet supported on Linux; every use asks97you to approve it first.9899## Control access to your local computer100101The shared Grok Bot computer runs in the cloud. Access to the Mac or Windows102computer in front of you is a separate capability.103104In **Settings → General → Bot → Execution on Local Computer**, choose105**Ask every time**, **Always allow**, or **Never allow**. Once your account has106registered computers, the choice moves to **Settings → Computer → Computers**,107where each computer has its own **Execution on this computer** setting.108109The default is **Ask every time**. Use **Never allow** unless a Bot has a110specific reason to work on your local files. Your team admin can cap this111setting for the whole team; when the team's policy is stricter than yours, the112team's applies. These settings do not prevent the Bot from using its cloud113computer.114115The first time a Bot asks to run a command on your computer, the conversation116shows **Allow Grok Bot and all Bots to run commands on your local computer?**117with **Always allow**, **Allow once**, **Never**, and **Deny once** (Esc).118**Always allow** and **Never** set **Execution on Local Computer** for every119Bot, and you can change the setting later in Settings. If your team's admin has120set a stricter ceiling, **Always allow** is unavailable.121122## Understand the shared-computer boundary123124All of your Bots share one cloud computer assigned to your user account. Files,125browser sessions, and command line credentials on that computer are available126across your Bot roster.127128* Do not use separate Bots as a security boundary.129* Sign out of a service when it should no longer be available.130* Remove sensitive temporary files after the work is complete.131* Delete a connector or revoke its authorization in the source service when132  access is no longer needed.133134Do not treat this user assignment as a guarantee that is broader than Cursor's135published security documentation. Review current infrastructure and encryption136controls there.137138## Sharing a Bot is not a security boundary139140A public share link lets others copy the Bot's configuration. It does not share141your computer or logins. Still, do not put secrets, customer data, or internal142URLs in a Bot you share. See [Share a Bot](/grok-bot/bots#share-a-bot) and the143[third-party bot terms](https://x.ai/legal/bot-sharing-terms).144145## Cursor account and data settings146147Grok Bot uses Cursor authentication and account data settings.148149* Grok Bot requires data storage and does not support Legacy Privacy Mode.150* Privacy and data-sharing choices are managed through Cursor account settings151  and, when required, the Grok Bot access flow.152* Training opt-out follows the applicable Cursor account and privacy settings.153* Review the current [Cursor Privacy Policy](https://cursor.com/privacy) and154  [security information](https://cursor.com/security) for contractual details.155156Organization administrators can restrict local-computer execution and may157provide managed setup for the cloud computer. Available controls depend on the158organization's rollout and plan.159160## Remove access and working data161162When a project or login should no longer be available:1631641. Pause or delete related routines.1652. Sign out of websites on the shared computer.1663. Uninstall connectors and revoke their authorization in the source service.1674. Remove sensitive project files from `/workspace`.1685. Hide or delete Bots that should no longer appear in Grok Bot.1696. Use the account settings flow if you need to delete the Cursor account.170171Deleting a Bot does not remove shared-computer files or browser sessions.172Backend retention and account deletion follow the applicable Cursor terms.173174## Use a least-privilege setup175176* Connect only the tools a workflow needs.177* Use scoped service accounts where the source system supports them.178* Start with read-only tasks and draft outputs.179* Keep sending, publishing, purchasing, deletion, and production changes behind180  approval.181* Review installed connectors and active routines regularly.182* Pause a routine when its source system or expected workflow changes.183* Preserve source links and an action log for important decisions.184
Files main
Menu

Theme