Grok Bot template vs. Team Bot — which do I need?
Last checked October 28, 2026 · Grok Bot changes often
Use a template when each person should have their own independent copy — copies share nothing after they are made, not memory, files, logins or history. Use a Team Bot when several people need to work with the same Bot and its shared context. Team Bots launched in public beta in October 2026 after being the top request from co-founders and teams.
| Template | Team Bot | |
|---|---|---|
| Who uses it | Each recipient, separately | The whole team |
| Memory and files | Each copy has its own | Shared |
| After changes | Copies do not update | Everyone sees the same Bot |
| Logins | Each person connects their own | Set up by the team |
| Good for | Sharing a workflow publicly | A company's Sales, Ops or Support Bot |
Why it matters
Before Team Bots, two co-founders who wanted to talk to the same "Sales" and "Ops" Bots could only share copies, which drifted apart immediately. That forum thread drew a long line of "+1, our number one blocker" replies until staff announced Team Bots in public beta.
Templates still matter
- Public sharing across companies or with the community.
- Giving teammates a starting point they will customise.
- Backing up a Bot's setup.
On team and enterprise plans, admins decide whether members can publish templates publicly.
Team Bot tips
- Give one Bot ownership of one end-to-end outcome.
- Keep external actions behind approval rules; a shared Bot acts on behalf of more people.
- Owners and managers edit the description under About in the Bot's details.