Give each staff member their own bot safely
Roll out a separate bot to each staff member with their own sign-ins, a shared starter rulebook, and a monthly check that no bot can act as someone else.
Try asking: “Write a starter rulebook every staff member's bot gets.”
For owners giving bots to a team, especially after a bot signed in with another person's account · Grok Bot, Claude or ChatGPT · Intermediate
Tested Nov 2, 2026See the receipt
Copy the prompt
Fill in the [brackets] after you paste it.
Write a starter rulebook every staff member's bot gets. Use only my rules.
Our business: [ONE LINE]
What any staff bot may do: [LIST]
What needs the person's approval: [LIST]
What no staff bot may ever do: [e.g. use another person's login, touch payroll, pay anything]
Under 250 words, 4 headings: May do, Ask first, Never, If unsure. Add the rule: only use the accounts of the person you work for.Copied. Paste it into Grok Bot next.
Free PDF
Get this setup as a PDF
Enter your email and a print-ready copy of this setup opens here, to save as a PDF. The free starter pack opens too. Tap confirm in the email that follows to get occasional new setups. Unsubscribe anytime.
Already a subscriber? Unlock it on this device
Free PDF
A confirmation email is on its way too: tap confirm in it to get new setups by email.
Three ways to run this setup
Free
Copy and paste it yourself
Copy the prompt above into ChatGPT, Claude or Grok. It drafts. You approve.
Go to the prompt$9 once
Complete Pack
One payment, no membership. Opens the pack pages: Bot Safety Checklist, Second Brain Starter Vault, Voice File Starter, Tested Grok Bot prompt pack, Write it as code prompts.
See the Complete PackFree to start, VIP $19 a month
Save it as a bot in the guided setup app
The app turns this setup into a bot with the draft-only rules. 3 setups build free; the rest are part of VIP. A human reviews a prompt or setup for you within 24 hours, up to 2 a month.
Build it in the app
What you get back
Illustrative. Your results will differ.
- Starter set: rulebook, morning inbox brief, approval before send
- Monthly check: Sam's bot can reach Sam's email and calendar only. OK.
- Flag: front desk bot still signed into the owner's email. Remove.
3 steps
- Copy the prompt.
- Paste it into Grok Bot.
- Fill in the [brackets], then read the answer before you send or use it.
Quick answer
One person, one bot, one set of sign-ins. Never let a bot use a colleague's login. Give everyone the same starter rulebook and routines, let each person add their own, and check monthly which accounts each bot can reach.
How do you set it up?
Tools
- Your bot platform's team or user settings
- A starter rulebook
- A list of each person's accounts
Steps
- Decide the starter set every person gets: the rulebook, approvals, and 1 to 3 standard routines.
- Give each person their own bot and computer or workspace. xAI notes the bot's computer shares its browser, files and credentials, so shared machines mean shared logins.
- Each person signs in their own accounts. Nobody signs in for someone else.
- Use the prompt below to write the starter rulebook once.
- Let each person add routines for their own job, within the rulebook.
- Monthly: list which accounts each bot can reach and remove anything that is not that person's.
Where to paste this prompt
Grok Bot → paste the prompt into a chat, or save it as a routine or scheduled task if the job repeats
More ways to run it
Which chat tools work with this prompt?
Paste the prompt into any of these assistants (free or paid tiers).
- Grok Bot
- Claude
- ChatGPT
The receipt
Ran on Grok Bot, Nov 2, 2026: a 132-word starter rulebook with the 4 headings, and a real access check on one bot that flagged 6 account groups it did not need. No human staff; other bots' access lists were not checked.
What this sticker meansAbout 1 hour to set up for a small team.
Last updated: · Last reviewed:
Before you use this
What it is allowed to do: Read-only. Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
At a glance: time, cost and difficulty
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Read-only
Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
- Time saved (estimate)
- About 1 hour to set up for a small team.
- Difficulty
- Intermediate
- Tools needed
- Grok Bot
- Typical cost
- Prices: Not stated in sources.
Reviewed Nov 2, 2026
Basis (estimate): Estimate only: based on the steps above, not timed.
What went wrong in the test, and the rule that fixed it
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- One shared bot computer for the whole team.
- Signing in a teammate's account to get a bot working.
- No list of what each bot can reach.
What tips make it smoother?
- The starter set keeps quality even; personal routines keep people using it.
- Remove bot access the day someone leaves.
- Keep payroll and HR out of staff bots entirely.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read xAI’s write-up (docs.x.ai)
xAI: Grok Bot computer and apps: one computer per user; the browser, files and credentials on that computer are shared by the bot (as cited elsewhere in this catalog)
- Read xAI’s write-up (docs.x.ai)
xAI: Grok Bot approvals, security and privacy: approvals for sends, spend and purchases; shared computer, local execution settings and connector hygiene (as cited elsewhere in this catalog)
Common questions
- Can staff share one AI bot?
- It is safer for each person to have their own bot and sign-ins, so no bot acts with someone else's account.
- How do I keep quality consistent?
- Give everyone the same starter rulebook and routines, then let them add their own.
- How often should I check access?
- Monthly, and the day anyone leaves.
Free kit by email
Get the free kit by email
The starter pack and the Portable AI Office, sent to your inbox. New setups by email after that. Unsubscribe any time.
What to do next
- Set guardrails before an AI agent gets access
Write a one-page rulebook for an AI agent before it touches your accounts: what it can read, what it can only draft, what always needs your approval, and what it must never do.
- Limit what staff and bots can see in your books
Set each person's and each AI connection's access to your books to the minimum the job needs, keep HR and payroll data out of shared bots, and review it monthly.
- Organize your bots like an org chart
Lay out your bots like an org chart: one coordinator, specialists with one job each, clear handoffs, and your approval on anything that goes out.
Have a setup that works? Submit it. We credit sources and write it up in plain language.