Set up Grok Bot with least access, then build four bots for script revisions, breakdowns and call sheets, shot tests, and post notes and clearances. Each runs on a tested routine and waits for your approval.
What you will be able to do
- Pick the right tool for each production task: Decide whether a job belongs in Grok Bot, a Custom Agent in the Grok chat app or a bot built on the Grok API. Check which plans include Grok Bot on the official pricing page, because plans and prices change.
- Set Grok Bot up with the least access that works: Turn Auto-review on, with Ask first rules for sending, posting, purchasing, deleting and permission changes. Set Execution on this computer to Never allow, switch off app tools you don't need, save no cards in Vault and keep one Bot per production.
- Write instructions that tell a Bot when to stop: Write a setup message that names the Bot's one job, its sources, its people, what it may change, what it must never touch and when it has to ask. For example, it asks the script supervisor which revision is current before it treats any draft as the baseline.
- Build four production bots and put them on routines: Using one sample scene, build a script revision desk, a breakdown and call-sheet bot, a shot-test register and a post notes and clearances tracker. Save each one as a skill and check it with Test before you rely on it.
- Share a Team Bot with your production: Share a Bot with your team and bring it into Slack. Attach only the apps, files and secrets that everyone with access may use, and know whose accounts and usage each reply draws on.
- Review what your bots actually did: Use approval cards, run history, memory checks and evidence requests to catch invented availability, costs or safety instructions, old notes attached to a replacement shot, and accepted work that was quietly overwritten.
Taught at learn.c-o-u-r-s-e-s.com: lessons that adapt to your level, an AI tutor you can ask anything, quizzes and flashcards, and a certificate when you finish.
