Grok Team Bots let one person set up a Grok Bot with files, skills and app connections, then publish it so the whole team can use it in the Grok Bot app or in Slack. xAI launched them on September 28, 2026, in public beta on Cursor Teams and Enterprise plans. Each teammate gets a private chat. The team shares the setup and a team memory.
Yesterday we covered what Grok Bot is. This post is the team version: what a Team Bot can see, what it remembers, who controls it, how it compares with OpenAI, Anthropic and Google, and five questions for an agency or association before it joins Slack.
The short version: a Team Bot is one setup that runs in many places. When you chat with it in the app, it runs on your own cloud computer, with your browser logins. In a Slack channel, it runs on a separate shared computer. Plugins that use a sign-in act as whoever is asking. Plugins set up with a key give everyone the same access. Only the owner can change the setup, and on the Teams plan there are no audit logs. Plan your channels and keys with that in mind.
What Grok Team Bots are
xAI’s launch post calls them "Grok Bots that work and learn alongside your team." The Team Bots documentation (updated October 2, 2026) puts it simply: "A Team Bot is one Bot that your whole team talks to."
The owner gives the Bot four kinds of setup:
- Plugins: connections to apps. xAI’s examples include Salesforce, Notion and GitHub.
- Secrets: up to 25 stored credentials for services without a plugin.
- Skills: repeatable team processes every teammate can use.
- Files: reference material such as a brand guide, in text formats up to 256,000 characters each.
You build a Team Bot in the desktop app, or publish an existing personal Bot to the team. Teammates then reach it in the desktop app, the mobile app or Slack.
How a Team Bot differs from a personal Grok Bot
A Team Bot has one owner and many users. The table sets out the differences xAI documents.
| Question | Personal Grok Bot | Grok Team Bots |
|---|---|---|
| Who uses it | One person | Every teammate it is published to |
| Who changes the setup | The owner | Only the owner; changes reach everyone |
| Where it runs | The owner’s cloud computer | Each user’s own computer, or a shared computer for Slack channels |
| Memory | One memory | Team memory plus private notes per person |
| Usage | The owner’s allowance | Each teammate’s own allowance |
The privacy line is clear in the docs: "The owner can’t read teammates’ chats, and teammates can’t read the owner’s."
Routines stay personal. xAI says a routine "runs as them, reports in their chat, and only they can see or change it."
Where Grok Team Bots run, and what they can see
A Team Bot does not live on one machine. The docs list three places it runs:
- The owner’s own chat runs on the owner’s computer.
- A teammate’s chat in the app, or their one-to-one Slack DM, runs on “that teammate’s own computer.”
- Slack channels, group DMs and threads run on “one shared computer for that Bot, separate from the owner’s and every teammate’s.”
Now add what xAI’s computer and apps page says about each person’s computer: "Every Bot on your account uses the same computer." It adds: "Browser cookies and signed-in sessions are shared," "Files are visible to every Bot," and "Command-line credentials are shared."
Put those together. When you chat with a Team Bot in the app, it works in your browser, with every site you or your other Bots signed in to. The owner’s skills and instructions run there too, acting on your logins.
The upside is that one person’s access does not leak to another person’s chat. xAI says a plugin that needs a sign-in "uses the account of whoever is talking to the Bot. A Team Bot never lends one person’s access to another."
xAI’s docs do not say which logins, if any, sit on the shared Slack channel computer. Ask before you rely on it.
What Grok Team Bots remember
Team Bots keep two kinds of memory. "Team memory is read by every teammate’s conversation," xAI says. "Notes with each person are private to that person."
Something becomes team memory when someone tells the Bot the whole team should have it. To see what it saved for the team, you ask it in chat. To correct or remove something, you tell it.
That is a light process. Any teammate can add to team memory, and the docs describe no admin screen to review it.
xAI’s Bots page says: "Memory is not a substitute for an authoritative source." Membership rules, rates and deadlines belong in the system of record, not in the Bot’s memory.
One more choice comes at setup. When you publish a personal Bot whose memories are mostly about you, xAI asks how the Team Bot should start. You can copy the Bot’s chat and memories, or start fresh. For a shared Bot, start fresh.
Slack, and the apps Grok Team Bots connect to
Each published Team Bot gets its own Slack app. The owner chooses "Bring to your team’s Slack," connects the workspace and approves Cursor in Slack. Then you invite the Bot to channels, for example with /invite @BotName.
It answers direct messages and @mentions in channels it has joined, but "only people who have linked their Slack account to Cursor." Only the owner can remove it from Slack.
Slack is the only chat app in xAI’s Team Bots docs as of October 6, 2026. We found no mention of Microsoft Teams or Google Chat. If your organization runs on Teams, Grok Team Bots are an app-only product for now.
For connected apps, xAI’s launch post names Notion, Linear, Hex, Datadog, Cursor, Statsig, Databricks and Gong, plus Salesforce and GitHub. Your Cursor connector policy decides what your team can use.
Plugins split two ways. A plugin that signs in with OAuth asks each teammate to connect their own account. A plugin set up "with a key or token" uses "the Bot’s own credential, the same for everyone." That second kind is the one to watch.
Who controls a Team Bot: owners, admins and plans
The owner controls the setup. "Only the owner can change this setup, and every change reaches all teammates," the docs say. The owner can also Unpublish, which removes access until the Bot is published again, with chats and routines restored.
Team admins work from the Cursor dashboard under Manage Team Bots. Per Cursor’s team docs, an admin can add a Team Bot to the sidebar of the whole team, chosen groups or no one. Members who get it this way cannot remove it. Admins can also delete a Team Bot for everyone.
Deleting is final. xAI says teammates lose the Bot "along with their chats and routines on it. This can’t be undone."
Plan matters. xAI’s teams and enterprises page (updated October 1, 2026) lists audit logs, enforced Auto-review, Network Controls and Action Recording as Enterprise only. On Enterprise, audit logs record Team Bot creation, publishing, unpublishing, deletion, skill changes and Slack account links. On Teams, you have none of that.
We found no documented control that stops a Teams member from publishing a Team Bot. Nor do the docs say what happens to a Team Bot when its owner leaves.
What Grok Team Bots cost, and how data is kept
Team Bots have no separate price. They come with the plans that include Grok Bot. Cursor’s pricing page lists Teams at $40 per user per month, with Standard and Premium seats, and Enterprise at custom pricing.
Usage follows the person. xAI says a teammate’s use "counts against that teammate’s own Grok Bot allowance, not the owner’s." Weekly allowances are not published.
On data, the Team Bots docs give no retention period. Cursor’s Grok Bot security page fills in some of it:
- Action Recording, where turned on, keeps Bot actions for 90 days.
- After the service ends, data “is deleted or returned within 30 days of written direction.”
- “Grok Bot computers run in the United States today.” Cursor’s US data residency option does not apply to Grok Bot by default.
How Grok Team Bots compare with OpenAI, Anthropic and Google
This table uses only vendor documentation and our earlier coverage. It does not rank the products.
| Question | Grok Team Bots | Claude Tag | OpenAI dots and @ChatGPT |
|---|---|---|---|
| Chat apps | Slack | Slack | Slack and Microsoft Teams |
| Plans | Cursor Teams and Enterprise, beta | Claude Team and Enterprise, beta | Dots: Pro, Business Premium, Enterprise beta; @ChatGPT: Business, Enterprise |
| Memory | Team memory plus private notes | Per channel and per workspace | Dots: own memories; reset deletes the dot |
| Who sets access | The Bot’s owner, within Cursor policy | Organization owners and Claude Tag admins | Workspace admins |
Anthropic’s Claude Tag help page says it "keeps context per channel and per workspace." Organization owners can review, edit and delete that channel memory, which Grok’s docs do not offer. We covered the launch in our Claude Tag post.
On the OpenAI side, dots can join Slack and Teams with an admin permission. @ChatGPT in Slack and Teams "does not inherit a person’s file, app, or private-channel access."
Google’s nearest piece is Gemini Spark, a personal agent. The Google pages we checked describe no shared team version in Slack or Chat. Its shared building block is Workspace skills, covered in Gemini skills replace Gems.
Five setup questions before Grok Team Bots join your Slack
For an agency or association, answer these first.
- Who owns it? Only the owner can change the setup or remove it from Slack. Pick someone who will stay, and ask Cursor what happens if they leave.
- Which plugins use a shared key? Key-based plugins and secrets give every teammate the same access. Use personal sign-in plugins for anything with member or donor data.
- Which channels, and who is in them? Channel replies are posted where the channel can see them. Keep the Bot out of channels with clients, guests or board members until you have tested it.
- What goes into team memory? Start fresh, not from a personal Bot. Agree on who may tell the Bot to remember something for the team, and check what it holds each month.
- Is Teams enough? Without Enterprise you have no audit log of Team Bot changes. If you need that record, budget for Enterprise or wait.
Agencies should also keep one Team Bot per client. Our guide to where AI agents run covers the wider cloud and local questions.
Frequently Asked Questions
What are Grok Team Bots?
They are Grok Bots that one person sets up and publishes to a team. Everyone then chats with the same Bot, with the same plugins, skills and files, in the Grok Bot app or in Slack. xAI launched them in public beta on September 28, 2026.
Which plans include Grok Team Bots?
xAI says Team Bots are in public beta on Teams and Enterprise plans. That means Cursor Teams, listed at $40 per user per month, or Cursor Enterprise at custom pricing. There is no separate Team Bots price.
Can the owner of a Team Bot read my chats with it?
No. xAI’s docs say the owner cannot read teammates’ chats, and teammates cannot read the owner’s. Your private notes stay private, but anything saved to team memory is read by every teammate’s conversation.
Does a Team Bot use my logins?
In the app or a one-to-one Slack DM, it runs on your own cloud computer. All your Bots share that computer’s browser sessions, files and command-line credentials, so the Team Bot works with your signed-in sessions.
Do Grok Team Bots work in Microsoft Teams?
Not as of October 6, 2026. xAI’s Team Bots docs describe Slack only.
Can a Teams admin see what a Team Bot did?
Not through audit logs. Audit logs and Action Recording are Enterprise features. A Teams admin can choose who gets a Team Bot in their sidebar and can delete a Team Bot for everyone.
How do I remove something from team memory?
Tell the Bot. xAI says to correct or remove something, you tell it, and to see what it saved for the team, you ask it in chat. The docs describe no separate admin screen for team memory.
What happens when a Team Bot is deleted?
The Bot is removed for the whole team, with teammates’ chats and routines on it, and xAI says it cannot be undone. Unpublish is the reversible option: access returns, with chats and routines, when the owner publishes again.
How are Grok Team Bots different from Claude Tag?
Both are Slack agents in beta on team plans. Claude Tag keeps context per channel and workspace, and owners can review, edit and delete channel memory. Grok Team Bots keep team memory plus private notes, managed by talking to the Bot.
