METAGROK
GROK BOT / share-grok-bot-roster-with-teammates

Share one Grok Bot roster across teammates

share-grok-bot-roster-with-teammates

Use this when your team wants the same Grok Bots, with the same instructions and files, and each person keeps a private chat. Grok Bot has two ways to share a Bot. A template gives each person a separate copy. A Team Bot is one live shared Bot that everyone chats with. xAI's launch post places Team Bots in public beta on Teams and Enterprise plans. docs.x.ai/grok-bot/team-bots says they are available to members of a team. This page names both and does not pick one.

Share a copy with a template

Sharing a Bot template gives the recipient a copy of the Bot's setup. The docs say "Adding a shared Bot creates a copy on the recipient's account. It does not give them your computer, logins, or conversation history" (docs.x.ai/grok-bot/bots, checked 2026-09-29). The FAQ describes the same flow: open the Share menu and choose Create template (docs.x.ai/grok-bot/faq, checked 2026-09-29).

Once the copy exists, edits, memories, and files on your Bot and on theirs change independently. The link options are Public link or Team-only, and Team-only opens only for members of your team. Team-only is a link setting for template copies and does not make the Bot shared. See Share a Grok Bot for the copy steps.

Share one live Bot with a Team Bot

xAI announced Team Bots on Sep 28, 2026: shared Grok Bots that work and learn alongside a team, available in public beta on Teams and Enterprise plans (x.ai/news/team-bots, checked 2026-09-29). The post says everyone gets access to the same Bot and its expertise while working with it individually. Each person's conversations remain private, and the Bot keeps separate context and memories for each user while drawing on the skills shared across the team. The team can also invite the Bot into Slack through its own handle.

Team Bots is on docs.x.ai (checked Oct 8, 2026). After you publish, the owner can make teammates managers from Bot details > Setup > Managers. A manager can change setup (profile, skills, plugins, secrets, Slack app), receive secret requests in their own Grok Bot chat, save team skills, and add the Bot to Slack. Those setup changes reach the whole team. Only the owner can publish, unpublish, or delete. Teammates who are not managers cannot change setup. Slack setup still uses the owner's Slack connection, so the owner has to connect Slack first. See Set up a Team Bot in Grok Bot for the add-manager clicks. Cursor's help page still describes Create new Team Bot and Publish to Team (cursor.com/help/grok-bot/team-bots, checked 2026-09-29).

Choose between the two

  1. Pick a Team Bot when the team should work from one Bot with shared plugins, credentials, and memories. The launch post names Teams and Enterprise. docs.x.ai says members of a team.
  2. Pick a template when each person should own an independent Bot that starts from the same setup, or when Team Bots are not available on your account. The launch post does not say individual plans get Team Bots.
  3. Keep the durable playbook in Notion, Drive, or git either way, so template copies can re-read the same source after they drift.
  4. Reconnect plugins on each teammate's own account for template copies. Shared-computer sessions on one account give no multi-user security boundary (approvals, security, and privacy, checked 2026-09-29).

Earlier forum answer

On Aug 30, 2026, Cursor staff (Colin) replied on the forum thread that sharing a Bot creates a copy and that team collaboration on the same Bots was being worked on (forum.cursor.com). On Sep 8, 2026 he said there was no ETA. Both replies came before the Sep 28 announcement.

Related

Pitfalls

  • Treating a template link as live sync. Copies diverge as soon as either side edits memory or files.
  • Putting several people on one Cursor login. That is account sharing and gives no separate chats or approvals.
  • Putting a personal API key into a Team Bot. Everyone who chats with the Bot can use the credentials the owner or a manager adds.
  • Confusing this with Microsoft Teams "message humans as the Bot", which remains a feature request without a staff product answer.