Short answer: Grok Bot Team Bots are Grok Bots that a whole team shares. One person, the owner, sets the Bot up once with plugins, secrets, skills and files, then publishes it, and every teammate talks to it in their own private chat from the Grok Bot desktop app, the iOS app or Slack. SpaceXAI launched Team Bots on September 28, 2026, in public beta on Teams and Enterprise plans (SpaceXAI).
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, how sign-ins and secrets work, what it costs and the security limits worth knowing before you roll one out.
What are Grok Bot Team Bots?
SpaceXAI's documentation defines a Team Bot as "one Bot that your whole team talks to" (docs). The launch post describes four ingredients:
- 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 shared job. The documentation gives examples: answering metrics questions from a data warehouse, keeping docs current as pull requests ship, triaging requests posted in a Slack channel or answering internal helpdesk questions from a knowledge base. For an everyday assistant that works from your own accounts and memories, SpaceXAI still recommends a personal Bot.
What is shared and what stays private?
| Element | Shared with the team | Private |
|---|---|---|
| Plugins, secrets, skills and files | Yes. The owner sets them up and every change reaches all teammates | — |
| Team memory | Yes. Every teammate's conversation reads it | — |
| Notes with each person | — | Yes. They follow that person across the app and Slack DMs |
| Chats | — | Yes. Each teammate has their own chat and the owner can't read it |
| Routines | — | Yes. A routine runs as the person who set it up |
Only the owner can change the setup or delete the Bot. Teammates can pin it, hide it and create their own routines with it, but they can't edit its shared plugins, secrets, skills or files. The Bot saves a fact to team memory only when someone says the whole team should have it, and it tells you when it does.
How do sign-ins and secrets work?
How a plugin signs in decides whose access the Bot uses:
- Plugins that sign in with an account (OAuth) use the account of the person talking to the Bot. Each teammate connects their own account the first time they need it. The documentation is explicit: "A Team Bot never lends one person's access to another."
- Plugins configured with a key or token use the Bot's own credential, the same for everyone.
- Secrets are encrypted, and nobody sees their values, not even the Bot, which replaces them with
[REDACTED]in its outputs. But the Bot can use every secret in any teammate's conversation, so the documentation tells owners to "treat a secret as access you are giving the whole team" and to prefer scoped, read-only service-account keys. A Team Bot holds up to 25 secrets.
The documentation's own example shows the pattern: a Bot reads Datadog alerts with a read-only key that nobody has to sign in to, and files Linear tickets through a plugin that each teammate connects, so every ticket is created by the person who asked for it.
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:
- In the owner's own chat, it uses the owner's computer.
- In a teammate's app chat or 1:1 Slack DM, it uses that teammate's own computer.
- In Slack channels, group DMs and threads, it uses one shared computer for that Bot, separate from everyone's personal machine.
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 (Grok Bot FAQ). For Slack channels, the documentation warns against sharing anything in a thread that shouldn't be visible to everyone in that channel.
How do Team Bots work in Slack?
A published Team Bot can have its own Slack app, named after the Bot, which posts as itself rather than as the owner. Teammates DM it or @mention it. In a channel, it answers when someone mentions it and then follows that thread. It only answers people who have linked their Slack account, so it knows whose accounts to use, and if your workspace requires approval for new apps, a Slack admin has to approve it first.
Who can use Team Bots, and what do they cost?
Team Bots are in public beta on Teams and Enterprise plans. Grok Bot itself is included in Cursor Pro, Pro+ and Ultra, SuperGrok, SuperGrok Plus and Heavy, Cursor Standard and Premium Teams, and Enterprise (Grok Bot). There is no separate price for Team Bots: when a teammate talks to one, the usage counts against that teammate's own Grok Bot allowance, and extra usage is billed on token cost.
Admins choose who gets each Team Bot in their sidebar by default: the whole team, nobody or specific groups. Some controls are Enterprise only, including the audit log of Team Bot events, Team Secrets, Network Controls and Action Recording (Grok Bot for teams and enterprises).
What can a team use them for?
SpaceXAI ships four pre-built 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 well-defined fixes. SpaceXAI says a five-person team 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 sign-off.
- Data Bot: answers one-off data questions with read-only queries 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 conversation where nobody can answer an approval card, a Team Bot runs without Auto-review unless your team enforces it, which is an Enterprise setting.
- 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 Team Bot removes it, with everyone's chats and routines on it, for the whole team. Unpublishing is the reversible option.
- Audit logs are Enterprise only. On a Teams plan you don't get the log of Team Bot events.
A safe starting pattern: give each Team Bot one job, prefer OAuth plugins so every action runs with the asker's own access, 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 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, Team Bots live in the Grok Bot app and Slack, while the Microsoft Teams connector is a tool a Bot can use.
How do you create a Team Bot?
- In the Grok Bot desktop app, choose New chat (Cmd/Ctrl+N) and then Create new Team Bot. To start from a Bot you already have, open its Share menu and choose Publish to Team.
- Tell the Bot what the team needs. It walks you through plugins, secrets, skills and files.
- Try it on real tasks and correct it as you go. Until you publish it, only you can see it.
- Choose Publish to team. Teammates find it under New chat → Team Bots, or through a link you send them.
- If your team works in Slack, choose Bring to your team's Slack in the Bot's details and invite it to the right channels.
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.