Grok Bot Team Bots: How Shared AI Teammates Work

Short answer: Grok Bot Team Bots are Grok Bots that a whole team shares. One person, the owner, sets the Bot up once with apps, secrets, skills and files, then shares it with the whole team or with chosen people and groups. Every teammate talks to it in their own private chat from the Grok Bot desktop app, the phone app or Slack. SpaceXAI launched Team Bots on September 28, 2026 (SpaceXAI).

A note on the name: the launch called them Team Bots, and as of October 28, 2026 the official documentation calls the feature Shared Bots (docs). This guide keeps "Team Bots" because that's the name most people search for, and says "shared Bot" when it describes what the docs say today.

Since August, Grok Bot has worked as a personal AI teammate: a Bot that signs in to your tools from its own cloud computer and comes back with finished work. If you are new to it, start with what is Grok Bot and how it works. Team Bots change who that work is for. Instead of each person teaching their own Bot the same process, a team teaches one Bot and everyone uses it. This guide covers what is shared and what stays private, whose accounts the Bot uses, what it costs and the security limits worth knowing before you roll one out.

What are Grok Bot Team Bots?

In the documentation, a Bot is either personal or shared. You share a Bot with your Cursor team "the way you'd share a doc": with everyone on the team, or only with certain people and groups. Sharing doesn't make a copy, and each person's chat with a shared Bot is private (docs, as of October 2026). Shared Bots always run in the cloud, so a Bot that runs on your own computer can't be shared.

The launch post describes four ingredients (SpaceXAI):

• Context: files, instructions and skills, from brand guides to internal documentation.
• Plugins: access to apps such as Salesforce, Notion and GitHub, connected by each person or configured for the whole team.
• Credentials: secrets that let the Bot call third party APIs that have no plugin.
• Memories: what the Bot learns, so it gets better at its role over time.

A shared Bot works best around one role or workflow your team shares, which is how the launch post frames it. If you want an everyday assistant that works from your own accounts and memories, keep that Bot personal.

What is shared and what stays private?

The Bot doesn't save anything about you personally for the team (docs, as of October 2026).

Who can change, share or delete a shared Bot?

As of October 2026, the documentation splits the roles like this (docs):

• Collaborators can chat with the Bot.
• Managers can also change how it works: its instructions, skills, memory and apps. The owner and Managers can change a shared Bot and can always use it.
• The owner is the only person who can delete a shared Bot from the sidebar. Deleting it removes it for the whole team, and it can't be undone.
• Team admins can also delete a shared Bot from Manage Shared Bots on the Grok Bot page of the Cursor dashboard (teams and enterprises).

Teammates can add a shared Bot to their sidebar and hide it again. Right click the Bot and choose Hide from sidebar. To add it back, choose + in the sidebar, then Browse shared Bots, and choose Add. If an admin used Auto-add to put the Bot in your sidebar, Hide from sidebar is not in its menu, and you cannot remove it (docs).

How do accounts and secrets work?

A shared Bot uses the apps and secrets its owner added, and those work the same for everyone who chats with it. On top of that, in your own chat with a shared Bot it can use your apps too, but it asks first. The approval card says Allow, then the app name (docs, as of October 2026):

• Allow once lets it use that account this time.
• Always allow remembers your answer, either for your messages to this Bot or for your messages to every Shared Bot.
• Skip means it doesn't use that account this time.

In Slack channels, threads and group chats, a shared Bot uses only its owner's apps, and it asks before it uses yours. A connected account always acts as the person the Bot is answering, and one teammate's connection is never used for someone else. To make every shared Bot ask again, open Settings > General > Shared Bots and choose Clear next to Clear connector preferences.

Secrets need more care, because they belong to the whole Bot. The documentation tells owners to only add keys and files they're happy for everyone they share it with to use, and the security guide repeats it (approvals, security and privacy). Prefer scoped, read only keys over personal credentials. The launch documentation capped a Team Bot at 25 secrets, and the current Shared Bots page no longer states a limit, so check the limit in the app.

Which computer does the work?

Every Grok Bot works on a cloud computer, and a shared Bot uses a different one depending on the conversation (docs, as of October 2026):

• In your own chat with a teammate's shared Bot, it usually works on your Grok Bot computer, so it can use the files there and the sites you're signed in to. Sometimes it uses a separate computer for that conversation, for example when your privacy mode is stricter than the owner's.
• In a Slack DM with the Bot, it also works on your own computer.
• In Slack channels, threads, group DMs and group chats, it uses one shared computer of its own.

This matters because in Grok Bot, isolation is per user, not per Bot: all of a person's Bots share one computer, with its files, browser and logins (teams and enterprises).

How do you talk to a shared Bot on desktop, phone and in group chats?

You can start a voice chat with a teammate's shared Bot on desktop. In your own chat with the Bot, choose Start voice chat (docs, as of November 6, 2026).

Shared Bots you have added also appear in the phone app. You can chat with them and answer their Allow cards. A shared Bot cannot be your primary Bot.

You can add a Bot a teammate shared with you to your own group chat. It cannot share a group with Bots that run on your own computer.

How do shared Bots work in Slack?

A shared Bot has its own Slack app and handle. The owner or a Manager adds it after sharing: click the Bot's name at the top of the chat, find Bring to your team's Slack and choose Connect. If it says Awaiting admin approval, a Slack workspace admin needs to approve the app first. Once it says Connected, teammates can message it directly or mention it in channels (docs, as of October 2026).

In a channel thread or a DM, the shared Bot acts for the teammate who mentioned it. Each teammate has to link their Slack account first, under Settings > General > Shared Bots. If you message the Bot before you link, it replies with steps. Approvals stay personal too: in a Slack thread the Bot posts a Review an action card with Allow once, Deny and View details, and only the person who asked can answer it.

Who can use shared Bots, and what do they cost?

Shared Bots are for members of a Cursor team who have Grok Bot. As of October 28, 2026, access works like this (plans and billing, teams and enterprises):

• The X Subscription: Grok Bot is included on Premium, Super and Ultra. Plus and Free don't include it.
• Legacy Cursor plans: it's included on every paid individual plan and on Cursor Teams, where every member has access.
• Other routes for individuals: you can link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, or take a seat on a Grok Business plan that you sign up for yourself.
• Enterprise: an admin turns Grok Bot on for the team from the Cursor dashboard. SpaceXAI's Grok Bot page says it's generally available for Enterprise and for teams on the Teams plan (Grok Bot).

There is no separate price for shared Bots. A shared Bot reply uses the Grok Bot usage of the person it's answering, in your own chat, in Slack and in group chats, so your own limits apply. The owner's usage pays for the owner's own messages and for Slack posts from apps or workflows that aren't linked to a Cursor account. When your allowance runs out, extra usage follows your plan's rules, which the plans page explains.

Admins control who gets each shared Bot. In Manage Shared Bots they can change who has access and use Auto-add to put a Bot in members' sidebars, for the whole team or for chosen groups. Some controls are Enterprise only, including audit logs, Team Secrets, Network Controls and Action Recording (Grok Bot for teams and enterprises).

What can a team use them for?

SpaceXAI ships four ready made Team Bots and explains how it uses each one internally:

• Customer Bot: one Bot per sales account, shared by the account executive, customer success manager, solutions architect and sales leader. It posts a weekday morning brief and drafts each person's next move.
• EPD Teammate: follows a project's Slack channels, files bugs in Linear and launches Cursor cloud agents for clearly defined fixes. SpaceXAI says a team of five used this setup to ship more than 100 pull requests a day while building Team Bots.
• Marketing Bot: reviews drafts against brand guidelines and takes approved website and SEO changes to a preview link for final approval.
• Data Bot: answers single data questions with queries that only read, in Databricks, using a library of skills for more than 45,000 tables.

The launch post also quotes Harper, an insurance company that says it built a Team Bot in 24 hours to find lapsed policies and saved its customers more than $120,000. That figure comes from a customer quoted by SpaceXAI, not from an independent review.

For more ideas you can adapt to a shared Bot, see these Grok Bot use cases.

What should you check before rolling one out?

A shared Bot multiplies both the benefits and the mistakes. These points come from SpaceXAI's own documentation:

• Approvals are not a hard boundary. Auto-review, the automated reviewer that lets an action proceed, asks for approval or denies it, "does not review every side effect": memory writes and most settings changes are examples (Grok Bot security). And in a chat where nobody can answer an approval, a shared Bot runs without Auto-review unless your team enforces it, which is an Enterprise setting (teams and enterprises).
• Prompt injection is reduced, not solved. Outside content is marked as untrusted, and the documentation says these controls "reduce, but do not eliminate, risk from malicious content". A Bot that reads Slack, email or tickets reads text written by people outside your team.
• Shared memory spreads mistakes too. A wrong fact saved to team memory reaches every teammate's conversation, so someone should own reviewing it.
• Deleting is permanent. Deleting a shared Bot removes it for your whole team, along with teammates' chats and routines on it. To stop sharing without deleting, open Share and remove access.
• Audit logs are Enterprise only. On a Teams plan you don't get the log of Bot events.

A safe starting pattern: give each shared Bot one job, keep secrets scoped and read only, and start with a low risk workflow such as data questions or internal documentation.

Is "Grok Bot Teams" the same as the Microsoft Teams integration?

No. Team Bots is the shared Bot feature launched on September 28. Grok also has a separate Microsoft Teams connector that can search and read channel and chat messages, send messages, reply to threads and create chats, always within the teams, channels and chats the user who is signed in can already access. In organizations that use Azure AD, an administrator may need to approve it first (Microsoft Teams connector). In short, shared Bots live in the Grok Bot app and Slack, while the Microsoft Teams connector is a tool a Bot can use.

Why can't I see or use a shared Bot?

The Shared Bots documentation lists these messages and what they mean (docs, as of November 6, 2026):

How do you create a Team Bot?

As of October 2026, the steps in the documentation are (docs):

1. In the Grok Bot sidebar, choose +, then Create a Bot, and give it a name. If you don't see Browse shared Bots under +, you aren't on a Cursor team or your app needs an update.
2. Tell the Bot what it should help the team with. A sentence is enough.
3. Follow its setup steps for apps, secrets, skills and files. Only add keys and files you're happy for everyone you share it with to use.
4. Click the Bot's name at the top of the chat and choose Share. Under Who has access, pick your team or People you invite, then add people or groups as Collaborator or Manager. You can also share a Bot you already have, since sharing doesn't duplicate it. Check its apps, secrets, skills and files first, because they work in every teammate's chat.
5. Teammates find it under + > Browse shared Bots and choose Add, or open a link you send them and choose Start a chat.
6. If your team works in Slack, choose Bring to your team's Slack in the Bot's details.

If you haven't created a Bot before, our guide on how to set up Grok Bot covers the account, the first Bot, routines and approvals. Changes since launch are tracked in our Grok Bot news page.

The skill behind a good Team Bot

Team Bots reward teams that can describe their work clearly: which job the Bot owns, which skills and data it needs, and what it must never do without asking. That is the same skill behind any AI agent rollout, and it can be learned. If you want to build it with mentors and real projects, compare our AI programs and pick the one that fits your starting point.