Can a business use Grok Bot as a shared bot for the whole team?

Short answer

Yes. On Team and Enterprise plans, the owner of a Grok Bot can publish it as a Team Bot and share it with the team, the organization or chosen people. Everyone talks to the same bot, with the same apps, skills and team memory, but each chat is private. What a teammate teaches it for the team waits until the owner or a Manager approves it under Review learnings.

What Grok Bot is, in one paragraph

Grok Bot is xAI’s agent product: a bot with its own persistent cloud computer (browser, file system, terminal) that works across your apps, such as Gmail, Google Drive, Slack and Notion, and can run routines on a schedule. It asks for approval before sensitive actions. It is a separate product from the Grok chat in a Grok Business workspace, and it runs on Cursor’s cloud: team administration happens in the Cursor dashboard.

Personal bots and Team Bots

A bot is either personal or a Team Bot. A Team Bot is shared the way you share a document: with your team, your whole organization, or only people and groups you invite. Sharing does not make copies. Everyone talks to the same bot.

Personal bot Team Bot
Who can use it Only the owner Whoever it is shared with
Where it runs Cloud, or your own computer Always in the cloud
Chats Yours Each person’s chat is private
Memory What it learned working with you Team memory and skills for everyone, plus private memory per person
Apps and secrets Yours The owner’s, the same for everyone; your own apps only after you allow it
Who pays for usage You The person it is answering

Team Bots are available on Team and Enterprise plans for members who have Grok Bot. The team needs at least one other member before you can share one.

Setting up a Team Bot

  1. Choose + in the sidebar, then Create a Bot, and name it.
  2. Tell it in a sentence what it should help the team with.
  3. Follow its setup steps for apps, secrets, skills and files. Only add what you are happy for everyone to use: these work in every teammate’s chat.
  4. Choose Publish when it says it is ready to share. Until then it is a draft only you can see.
  5. Use Share to pick who has access, and make someone a Manager if they should also change how the bot works.

Teammates find it under + → Browse shared Bots, through a link, or by asking their own bot whether a Team Bot exists for a job.

How a Team Bot learns for the team

This is the part that makes it more than a shared prompt. A Team Bot keeps team memory and skills. When a teammate teaches it something for the team, such as a better way to handle a request, the bot suggests the change instead of saving it straight away. The owner or a Manager sees it under Review learnings, labelled for example Updates the skill or Forgets a team memory, and chooses Approve or Reject. Changes the owner or a Manager makes in the bot’s main chat apply right away.

What the bot learns about you personally stays between you and the bot.

What admins control

  • Bot sharing: set to Everyone or Admins only on the team dashboard.
  • Allow Shared Logins: must be on before a Manager can let everyone act through one account in a shared connector. The alternative is that each teammate connects their own account.
  • Team Rules and connector policy apply on every plan; network controls, team secrets and enforced auto-review are Enterprise only.

The common misunderstanding

A Team Bot is shared memory for one bot, not for your company. The approved team memory lives inside that bot. It does not reach the Grok chat in your Business workspace, other Team Bots, or the ChatGPT and Claude windows your colleagues have open. A team with five bots for five jobs has five separate memories, each curated by its own owner. More on the different kinds of Grok memory in does Grok have memory.

What this means for a team

The review step is the right instinct: a team memory should not change because one person said so. But it puts the curation on whoever owns each bot, and it only works for work that goes through that bot. Decide per bot who the Manager is, and what belongs in its team memory versus in a shared document. For how this compares to an admin layer around Grok chat, see what is Grok Business.

Where Bombos fits

Bombos applies the same idea one level lower: one shared, traceable memory for the whole team, with team knowledge and learned rules, that every AI tool can use, including Grok, Claude, ChatGPT, Copilot and your own agents. It also reads what already sits in mail, documents and repos. It runs in our cloud or on your own server, and one person can try it first with their own agents.

Related questions

Which plans include Grok Bot?

On The X Subscription, Grok Bot is included on Premium ($30), Super ($100) and Ultra ($200), not on Plus. xAI's team docs also list access through a seat on a self-serve Grok Business plan, and on Teams plans every member has access.

Can the bot owner read my chats with a Team Bot?

No. xAI's docs state that each person's chat with a Team Bot is private: the owner and Managers cannot read it, and what the bot learns about you personally is not saved for the team.

Whose usage pays for a Team Bot reply?

The usage of the person it is answering, also in Slack and group chats. A reply to someone in Slack who has not linked an account or is not on the team uses the team's usage.

Can a Team Bot work in Slack or Microsoft Teams?

The owner or a Manager can connect a shared bot to Slack, where teammates can message or mention it. It can also be added to Microsoft Teams once a team admin has enabled Microsoft Teams on the Grok Bot page of the team dashboard.

Sources

  1. xAI docs: Team Bots
  2. xAI docs: Grok Bot for teams and enterprises
  3. xAI docs: Grok Bot overview
  4. xAI docs: Grok Bot on The X Subscription
  5. xAI docs: Use Grok Bot in Microsoft Teams
The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.