Set up a Team Bot in Grok Bot

Use this when you want one Grok Bot that your whole team works with from the same context, plugins, credentials, and memories, and each person still keeps a private conversation with it. That is a Team Bot. It is a live shared Bot, so it works differently from a shared Bot template, which gives each person a separate copy.

Check that your plan is eligible

xAI's launch post says Team Bots is "available today in public beta on Teams and Enterprise plans" (x.ai/news/team-bots, dated Sep 28, 2026, checked 2026-09-29). The post names no other plan.

Cursor's help page says that if Create new Team Bot does not appear after you choose New in the sidebar, Team Bots are not on for your team yet, or you are not on a Cursor team (cursor.com/help/grok-bot/team-bots, checked 2026-09-29).

For Enterprise, xAI's sources differ on how access starts. The Grok Bot FAQ says Enterprise access is rolling out and points to your Cursor account team (docs.x.ai/grok-bot/faq, checked 2026-09-29). The August plans announcement said to join a waitlist (x.ai/news/grok-bot-more-plans). Ask your Cursor account team which applies to you.

What a Team Bot holds

The launch post describes a Team Bot as a Grok Bot built around a role or workflow your team shares. It brings together four things:

• Context: relevant files, instructions, and skills, from brand guides to internal documentation.
• Plugins: they let the Bot work in applications such as Salesforce, Notion, and GitHub. Each person can connect them, or they can be configured for the whole team.
• Credentials: they let the Bot securely reach third-party APIs that have no plugin.
• Memories: they help the Bot retain what it learns and improve at its role over time.

Each person's conversations with the Bot remain private. The Bot keeps separate context and memories for each user while it draws on the skills shared across the team.

Build and publish one

xAI's launch post says you give the Bot access to the files, apps, and expertise it needs and then share it. It lists no menu steps, and the Grok Bot pages on docs.x.ai do not mention Team Bots as of 2026-09-29. The steps below are what Cursor's help page says, in Cursor's labels (cursor.com/help/grok-bot/team-bots, checked 2026-09-29). The xAI sources do not confirm these paths.

Cursor's help page says to:

1. Choose New in the sidebar, then Create new Team Bot. The page says this creates a Bot named New team bot and opens its chat.
2. Tell the Bot what it should help the team with. The page says a sentence is enough.
3. Follow the Bot's setup steps. The page says it asks for plugins, then secrets, then files, and advises adding only keys and files you are happy for the whole team to use.
4. Click the Bot's name at the top of the chat and choose Edit details to set a name and description. The page says teammates cannot see a Team Bot that still has the default name and no description.
5. Choose Publish to team when the Bot shows its ready card.

The page says teammates then find the Bot under New, then Team Bots, or through the link on the ready card. For an existing Bot, it says to open the Share menu and choose Publish to Team, which makes a separate team copy and walks you through secrets, memories, and routines while the original keeps working. It says Unpublish, in the Bot's name menu, stops sharing.

Bring it into Slack

The launch post says each Team Bot has its own handle. You invite it to a channel where everyone can ask questions, contribute context, and see its responses.

Cursor's help page says the owner adds the Bot after publishing: click the Bot's name, find Bring to your team's Slack, and choose Connect. It says Awaiting admin approval means a Slack workspace admin has to approve the app, and that each teammate then links their Slack account under Settings > General > Team Bots > Link. The xAI sources do not describe these steps.

Start from a pre-built Team Bot

The launch post lists four pre-built Team Bots to try: sales, product management, marketing, and data analytics. It describes them as Customer Bot, EPD Teammate, Marketing Bot, and Data Bot. It does not say where to open them in the app.

Where the sources stop

• The xAI launch post and docs.x.ai give no setup steps. Every click path above is what Cursor's help page says, and xAI has not confirmed it.
• Neither source gives a price or usage allowance for Team Bots. Cursor's page says a chat with a teammate's Team Bot uses the chatting person's own Grok Bot usage.
• The post does not say whether individual plans or SuperGrok subscriptions can use Team Bots. Do not assume they can.

Related

• All how-tos: How-to index.
• Context: Share a Grok Bot covers the template copy that gives each person a separate Bot.
• Context: Share one Grok Bot roster across teammates explains when to pick a copy and when to pick a Team Bot.
• Context: Store secrets securely in Grok Bot covers credentials before you put them in a shared Bot.

Pitfalls

• Putting a personal API key into a Team Bot. Cursor's help page says a Team Bot uses the secrets its owner added for everyone who chats with it.
• Publishing before the Bot has a name and description. Cursor's help page says teammates cannot see it.
• Expecting a shared template link to behave like a Team Bot. A template link gives each person a copy.
• Expecting Slack to work at once. Cursor's help page says the Connect step can wait for a Slack workspace admin to approve the app.