# Give each staff member their own bot safely

> Tested by AI Setups That Work. Small business · Intermediate · Operations. Updated 2026-11-02.
> 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.

Canonical page: https://www.aisetupsthatwork.com/setups/give-each-staff-member-their-own-bot-safely/

## What it does
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.

## Who it's for
Owners giving bots to a team, especially after a bot signed in with another person's account.

## Tools
- Your bot platform's team or user settings
- A starter rulebook
- A list of each person's accounts

## Steps
1. Decide the starter set every person gets: the rulebook, approvals, and 1 to 3 standard routines.
2. 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.
3. Each person signs in their own accounts. Nobody signs in for someone else.
4. Use the prompt below to write the starter rulebook once.
5. Let each person add routines for their own job, within the rulebook.
6. Monthly: list which accounts each bot can reach and remove anything that is not that person's.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
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.
```

## Guardrails
- What it touches: Connected mail, calendar, sheets, or chat. Scoped to this job (Your bot platform's team or user settings; A starter rulebook).
- Needs your OK: Send, pay, publish, and account changes stay with you. Treat agent output as drafts first.
- Safety level: Read-only
- 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.

## Tips
- 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.

## Estimates (labeled, not measured)
- Time saved: About 1 hour to set up for a small team.
- Money saved: Not stated in sources.
- Tool cost: Prices: Not stated in sources.

## Sources
Summaries use the public sources below, not independent verification.
- xAI: https://docs.x.ai/grok-bot/computer-and-apps (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))
- xAI: https://docs.x.ai/grok-bot/approvals-security-and-privacy (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))

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-give-each-staff-member-their-own-bot-safely

Related:
- [Set guardrails before an AI agent gets access](https://www.aisetupsthatwork.com/setups/set-guardrails-before-giving-an-ai-agent-access/index.md)
- [Limit what staff and bots can see in your books](https://www.aisetupsthatwork.com/setups/limit-what-staff-and-bots-can-see-in-your-books/index.md)
- [Organize your bots like an org chart](https://www.aisetupsthatwork.com/setups/organize-your-bots-like-an-org-chart/index.md)
