Home › Grok Bot lesson 2: Approvals, groups
Grok Bot lesson 2: Approvals, groups
A Bot can act in your apps, so the useful habit is to say where it must stop. Approvals, editable drafts and secure take-over steps keep the important actions in your hands.
Step by step
- State a boundary in the request, for example “draft it, don't send it” or “ask before changing anything”.
- When an approval card appears, check the target and values, then choose Allow once, Always allow or Deny.
- Review email and Slack drafts in the chat and choose Send or Discard.
- For passwords, 2FA codes and payments, choose Take over, finish the step yourself, then I'm done.
- For bigger jobs, start a group chat with two to six Bots (New chat → select Bots) and use @ to say who owns each step.
Try it: examples
- A request with a boundary
Reconcile the campaign data and draft a recommended budget change. Do not change the campaign or message the agency. Ask for approval after showing the current value, proposed value, and expected impact.
- Group kickoff
@Researcher gather the source material and link every claim. @Writer turn the findings into a launch draft. @Reviewer check the draft against the sources and list only blocking issues. Do not publish anything.
Good to know
- Set your own Ask first and Allow automatically rules under Settings → General → Auto-review; if both match, Ask first wins.
- Approvals from routines or other Bots expire after about 10 minutes and the action does not run.
- Never send a password or one-time code in ordinary chat.
- A “Stop now” message ends work, but does not undo actions already done.
Sources (official pages, read Nov 8, 2026)
Written from SpaceXSI's official documentation and product pages; we don't run hands-on tests. Features and limits vary by plan and country.