Turn a Bot into a team Bot your colleagues can use

How this helps you

Colleagues use your best workflow directly, so you stop being the bottleneck.

✦ Try it

Make a team Bot copy of yourself for my team. List the skills and connections the copy will have, and anything that will not carry over.

What they did

Matt Palmer explains team Bots, available on team and enterprise plans. His example is a simple marketing review Bot with two skills (writing revision and marketing copy review) that returns a before, an after and a why for any copy you send. To share it, you either tell the Bot to make a team Bot copy of itself, or click the share icon and choose share with your team. That creates a separate team copy; you can archive your personal one. You then copy a link to share it. Owners can edit the Bot, users can only use it. Teammates can also reach it inside Slack or Microsoft Teams. His later update added access lists to control who can use each team Bot.

Who it's for: Team and enterprise users who keep getting the same requests.

How to try it

Get a Bot working well for yourself first, with its method in skills.
Tell it: make a team Bot copy of yourself for my team. Or use the share icon and Share with your team.
Copy the link and send it to colleagues.
Invite co-owners who may edit it, and set the access list.

What to expect

A new team copy of the Bot with its own link and details page.

Common mistakes

Sharing a Bot whose rules only live in your head. Put the method in skills first.
Giving everyone owner rights. Keep a small group of owners.

Related tips

Let a team Bot answer requests in Slack: Install a team Bot in Slack so colleagues tag it directly, and give it a routine to catch missed tags.
One job per Bot: Give each Bot one job and a list of things it never does.
Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
Add a ready-made Bot from the Marketplace: Browse Bot templates at x.ai/bot/marketplace, read what each one includes, then add your own copy.
How the team uses its own Bot on support: It spots incidents and answers related tickets; a human approves the batch.
Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
Roll out Grok Bot to a team with admin guardrails: From the official admin video: set team rules, auto-review, plugin and network allow lists, then start with a pilot group before inviting everyone.
Share a finished Bot as a template without sharing your accounts: Share as template packages a Bot's rules, skills and routines. A privacy filter strips chat history, email addresses, account IDs, tokens and keys before you publish a link.
One governed Team Bot as the source of truth for sensitive data: Put a sensitive workflow, like checking exposure or compliance wording, in one admin-managed Team Bot that every personal Bot asks, instead of everyone building their own.