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 team, the whole organization or chosen people and groups. Every teammate talks to it in their own private chat from the Grok Bot desktop app or the phone app, and the owner or a Manager can also bring it into Slack and Microsoft Teams. SpaceXAI launched Team Bots on September 28, 2026 (SpaceXAI).

A note on the name: the launch called them Team Bots, and as of November 11, 2026 the official documentation calls them Team Bots again, after a stretch in October when it used Shared Bots (docs). A few screens in the app, such as Browse shared Bots, still say shared. They're the same thing, and this guide uses Team Bots throughout.

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 a Team Bot. You share a Bot "the way you'd share a doc": with your Cursor team, your whole organization, or only certain people and groups. Sharing doesn't make a copy, and each person's chat with a Team Bot is private (docs, as of November 11, 2026). Team 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 Team 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 November 11, 2026). Changes the owner or a Manager makes in the Bot's main chat apply right away.

Who can change, share or delete a Team Bot?

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

• Collaborators can chat with the Bot.
• Managers can also change how it works, share it with others and approve or reject what it learns from teammates. The owner and Managers can always use the Bot.
• The owner is the only person who can delete a Team Bot from the sidebar. Deleting it removes it for the whole team, and it can't be undone.
• Team admins can also delete a Team Bot from Manage Bots, under Shared Bots on the Grok Bot page of the Cursor dashboard. They also decide who may share Bots at all: the Bot sharing setting is either Everyone or Admins only. With Admins only, members see Only team admins can share Bots, and Bots already shared stay shared (docs).

Teammates can add a Team Bot to their sidebar and take it off again. Right click the Bot and choose Remove from sidebar. To add it back, choose + in the sidebar, then Browse shared Bots, and choose Add. If an admin added the Bot to your sidebar for you, Remove from sidebar is not in its menu, and you can't remove it (docs).

How do accounts and secrets work?

A Team 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 Team Bot it can use your apps too, but it asks first. The approval card says Allow, then the app name (docs, as of November 11, 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 Team Bot.
• Skip means it doesn't use that account this time.

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

A shared connector lets everyone use an app through one account, so teammates don't each have to connect it. The owner or a Manager sets it up in the Bot's details, under Setup, then Service accounts. They can keep individual accounts, give the Bot its own account, or share their own account, which means everyone who uses the Bot acts through it, changes included. Sharing a personal account only works after a team admin turns on Allow Shared Logins, which is off by default. The docs advise sharing only an account that holds nothing sensitive or private.

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 Team Bots page doesn't state a limit, so check the limit in the app.

Which computer does the work?

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

• In your own chat with a teammate's Team 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 Team Bot on desktop, phone and in group chats?

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

Team Bots you have added also appear in the phone app. You can chat with them and answer their Allow cards. A Team Bot can't be your primary Bot. To take one off your phone list, touch and hold it and choose Remove from sidebar.

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 Team Bots work in Slack?

A Team Bot has its own Slack app and handle. The owner or a Manager adds it after sharing: open the Bot's details, or choose Manage and look under Channels, 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 November 11, 2026).

In a channel thread or a DM, the Team Bot acts for the teammate who mentioned it. Each teammate should link their Slack account under Settings > General > Team Bots, so the Bot knows who they are and can use their apps. 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 talk to it in Slack depends on who it's shared with. If the Bot is shared with your whole organization, any full member of your Slack workspace can mention it in channels and threads, even without a seat on your team or a linked account. They're told once per thread that some features will be limited, and a DM still needs a linked account. Admins control this with the Slack Workspace Access setting, which is on by default. Slack guests, Slack Connect channels and other workspaces are never included. A Bot shared only with your team or with certain people answers only those people.

How do Team Bots work in Microsoft Teams?

As of November 11, 2026, the docs include a full setup for Microsoft Teams (Use Grok Bot in Microsoft Teams). It takes three people, in this order:

1. A Cursor team admin turns on Microsoft Teams from the Grok Bot page of the team dashboard, signing in with a Microsoft Teams or Global administrator account.
2. The Bot's owner or a Manager connects a published Bot from its details, under Bring to your team's Microsoft Teams.
3. A Microsoft Teams admin approves the Bot in the Teams admin center. Microsoft doesn't notify them, so send them the link the dialog shows.

After approval, Teams can take up to an hour to finish setting the Bot up. Then teammates can mention it in channels of teams it joined, add it to group chats or message it directly. It works the way it does in Slack: it acts for the person who asked, uses their usage and asks before risky actions. Each person links their Microsoft account the first time, or under Settings > General > Team Bots.

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

Team 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 Team Bots. A Team 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 Team Bot. In Manage Bots, under Shared Bots on the dashboard, 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 Team Bot, see these Grok Bot use cases.

What should you check before rolling one out?

A Team 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 Team 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 in team memory reaches every teammate's conversation. Learnings from teammates now wait for approval under Review learnings, so make sure the owner or a Manager actually checks that queue.
• Deleting is permanent. Deleting a Team 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 Team 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?

Not quite, and the overlap grew in November. Team Bots is the shared Bot feature launched on September 28, and a Team Bot can now live inside Microsoft Teams, as described above. Separately, Grok also has a 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 signed in user can already access. In organizations that use Azure AD, an administrator may need to approve it first (Microsoft Teams connector). In short, bringing a Team Bot into Microsoft Teams makes it a teammate people can mention there, while the connector is a tool a Bot uses to read and send Teams messages for you.

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

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

How do you create a Team Bot?

As of November 11, 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. Until you publish it, the Bot is a draft only you can see.
4. When the Bot says it's ready to share, choose Publish. Teammates can then find it.
5. To change who has access, choose Share at the top right of the Bot's chat. Under Who has access, pick your team, your whole organization (if your team is part of one) or People you invite, then add people or groups as Collaborator or Manager. If Share is disabled, your admin has limited sharing to admins. 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.
6. Teammates find it under + > Browse shared Bots and choose Add, or open a link you send them and choose Start a chat.
7. If your team works in Slack or Microsoft Teams, connect it from the Bot's details: Bring to your team's Slack or Bring to your team's Microsoft Teams.

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.