# Grok Bot for teams: Team Bots, usage and admin controls

On Cursor Teams every member gets Grok Bot. A Team Bot is one Bot the whole team chats with, each in a private chat, with each person spending their own usage.

*From Learn Grok Bot, an independent guide (not affiliated with SpaceXAI or Cursor). Web version: https://learngrokbot.com/teams Last verified: 2026-10-06.*

Every member of a Cursor Teams plan has Grok Bot with no admin step, and on Cursor Enterprise an admin turns it on. On either plan a team can publish Team Bots: one Bot everyone chats with, each person in a private chat and on their own usage.

**In short**

- **Cursor Teams**: every member gets Grok Bot, on a Standard or a Premium seat. There's no switch to turn it off.
- **Cursor Enterprise**: off until an admin turns it on, for the whole team or for chosen groups.
- A **Team Bot** is set up once by its owner and published to the team. Each person's chat with it is private, the owner's included.
- Whoever asks a Team Bot spends their own usage, not the owner's.
- Enforced Auto-review, network rules and audit logs are Enterprise only.

## Which plans include Grok Bot for a team?

Two Cursor plans are sold to teams, and both include Grok Bot. They differ in who switches it on and in how much an admin can control.

| Plan | Price | Who gets Grok Bot | Usage, in Cursor's words |
|---|---|---|---|
| **Cursor Teams**, Standard seat | $40 per user a month | Every member, with no admin step | "Follows the Teams plan allowance" |
| **Cursor Teams**, Premium seat | $120 per user a month | Every member, with no admin step | "Follows the Teams plan allowance" |
| **Cursor Enterprise** | Custom | Nobody, until an admin turns it on at cursor.com/dashboard/bot | "Managed by your admin" |

- Usage follows the seat. Moving a member to a Premium seat can raise their weekly usage.
- On-demand usage starts switched on for Teams, so work past a member's included usage is billed. [Usage limits](https://learngrokbot.com/usage-limits#on-demand) explains the on-demand limit.
- Two kinds of team don't get Grok Bot: one on a legacy request-based plan, and one that uses Privacy Mode (Legacy).

## What a Team Bot is

A Team Bot is one Bot that a whole team talks to. Team Bots have been in public beta on Cursor Teams and Enterprise since 28 September 2026, and every teammate finds them in the same place.

![The New chat list on a Cursor Teams account. Under To: Start a chat with, it lists Create new Bot, Create group chat, eight Bots whose names are blurred, and at the bottom a Team Bots row with an arrow](https://learngrokbot.com/assets/shots/teams-team-bots-row.jpg)

*On a team account, **New chat** ends with a **Team Bots** row. Published Team Bots are behind it, each with its owner's name. Click **Add**, then **Start a chat**.*

Image: Grok on YouTube (https://www.youtube.com/watch?v=8xXhE25vJZY)

A Team Bot differs from a Bot of your own in four ways:

- **One setup.** The owner adds its plugins, secrets, skills and files once, and every teammate's chat has them.
- **Private chats.** Each teammate gets their own chat. The owner can't read it, and teammates can't read the owner's.
- **Your own accounts.** A plugin that needs a sign-in uses the account of the person asking, so nobody borrows a teammate's access.
- **Two memories.** What someone says the whole team should know goes into team memory. What the Bot learns about you stays between you and the Bot.

Build one around a single shared job, such as answering questions from a knowledge base or sorting requests that land in one channel.

## Create and publish a Team Bot

You create a Team Bot on a computer, and nobody else can see it until you publish. The phone app can chat with a Team Bot and can't create one.

**Walkthrough: Create and publish a Team Bot**

### Step 1: Click Create new Team Bot

Click **New chat**, the **+** at the top of the sidebar, then **Team Bots**, then **Create new Team Bot**. The new Bot opens a chat and asks what it should help the team with. One sentence is enough.

![The Team Bots list in New chat. A search box reads Search Team Bots. One existing Team Bot is blurred, and under it is a row that reads Create new Team Bot](https://learngrokbot.com/assets/shots/teams-create-new-team-bot.jpg)

Image: Riley Brown on YouTube (https://www.youtube.com/watch?v=c9Z7ixVr4CU)

### Step 2: Work through the setup cards

The Bot hands you one numbered card at a time: plugins first, then secrets, skills and files. Add what the job needs, or click **Skip**. Put only keys and files on it that the whole team may use.

![A card in a Team Bot's chat titled Add plugins, marked Step 1 of 5. It reads: Tools it can use. Each teammate signs in with their own account, so no one shares a login. Slack, Notion and X each have a plus sign. Below are Skip and Add more plugins buttons](https://learngrokbot.com/assets/shots/teams-setup-card.jpg)

1. Each card shows its step, from 1 of 5 to 5 of 5.
2. Teammates sign in to a plugin with their own account. A key you add as a secret is different: everyone's chat uses the same one.
3. A **+** adds that plugin for everyone who uses the Bot.

Image: Riley Brown on YouTube (https://www.youtube.com/watch?v=c9Z7ixVr4CU)

### Step 3: Click Publish to team

Until you publish, the Bot's details read **Draft · Only you can see it**. Try it on a real task and correct it. When the last card says it's ready, click **Publish to team**.

![The last setup card, marked Step 5 of 5. Its title, with the Bot's name blurred, says the Bot is ready for your team. Under it: You built a Bot. Now your whole team gets a teammate. Two buttons: Publish to team and View details](https://learngrokbot.com/assets/shots/teams-publish-card.jpg)

Image: Riley Brown on YouTube (https://www.youtube.com/watch?v=c9Z7ixVr4CU)

> **You should see**
>
> The card now says the Bot is published and offers **Copy link**. Teammates find the Bot under **New chat**, then **Team Bots**.

If teammates can't find it, check its name and its description. A Team Bot that still has its default name and no description stays hidden.

### Who can change a Team Bot

| Who | What they can do |
|---|---|
| The owner | Change its name, description, plugins, secrets, skills, files and Slack app. **Unpublish** it or delete it. |
| **Managers** | The same setup changes. The owner adds them in the Bot's details once it's published. |
| A team admin | Choose who gets the Bot in their sidebar, and delete it. An admin can't change its setup. |
| Teammates | Pin it, hide it and set up routines with it. A routine on a Team Bot runs only for the person who made it. |

**Unpublish** takes the Bot away from teammates and keeps their chats for when you publish again. Deleting it removes those chats for good.

A published Team Bot can also join Slack as an app of its own. [A Team Bot in a channel](https://learngrokbot.com/slack#team-bot) has the steps and how it answers there.

## Whose usage does a request spend?

Publishing a Team Bot doesn't put the team on your bill. Each request spends the usage of the person who made it.

Diagram: Who pays when a Team Bot is used. A teammate who asks the Team Bot, in the app or in Slack, spends the teammate's own usage. The owner's own chats spend the owner's usage. A post from a Slack workflow, which no person sent, also spends the owner's usage.
- A teammate → The teammate's usage: asks in the app or Slack
- The owner → The owner's usage: asks
- A Slack workflow → The owner's usage: a post no person sent

*Every arrow is a request to the same Team Bot. It points at the usage that pays for the answer.*

- A teammate's chat with the Bot, in the app or in Slack, counts against that teammate's own usage.
- A routine on a Team Bot counts against the person who set it up.
- A Slack message that no linked teammate sent, such as a post from a workflow, counts against the owner.
- A teammate who has run out is told so in the chat or the thread. The Bot doesn't fall back on the owner's usage.

## What an admin controls

Admins manage Grok Bot on the Grok Bot page of the Cursor dashboard, at cursor.com/dashboard/bot, which members never see. Members see only the result, such as a rule they can't change.

![A list of Auto-review rules in Grok Bot's settings on a team account, with Action and Behavior columns. The first rule ends in a lock icon. The next two, whose text is blurred, end in edit and delete icons. Under the list: Team rules always apply. Your rules apply only to you. Built-in safety checks always apply](https://learngrokbot.com/assets/shots/teams-locked-rule.jpg)

1. A rule from the team ends in a lock. A member can't edit or delete it.
2. A member's own rules (blurred here) keep their edit and delete icons.
3. **Team rules always apply.**

Image: Grok on YouTube (https://www.youtube.com/watch?v=8xXhE25vJZY)

The table lists the main controls and the plan each one needs.

| Control | Teams | Enterprise | What it does |
|---|---|---|---|
| Turn Grok Bot on or off | No | Yes | For the whole team or for chosen groups. On Teams it's on for every member. |
| Team Rules | Yes | Yes | Short rules every member's Bots follow. Members can't turn them off. |
| Which plugins members can use | Yes | Yes | Grok Bot follows the team's Cursor plugin policy. A blocked plugin reads **Disabled by team admin**. |
| **Execution on Local Computer** | Yes | Yes | Whether Bots may work on members' own machines: **Always allow**, **Ask every time** or **Never allow**. |
| Cloud Agents and public templates | Yes | Yes | Whether Bots may hand coding work to Cursor Cloud Agents, and whether members may share a Bot template outside the team. |
| **Manage Team Bots** | Yes | Yes | Who gets each Team Bot in their sidebar by default, and deleting one. |
| **Enforce Auto-review**, and team Auto-review rules | No | Yes | Stops members turning Auto-review off, and adds rules they can't edit. |
| Network Controls | No | Yes | Which sites and addresses the team's cloud computers can reach. |
| Audit logs and Action Recording | No | Yes | A record of admin events, and of what Bots did. |
| A spend cap for Grok Bot alone | No | No | The account's on-demand limits cover Grok Bot and everything else together. |

## Decide before you invite the team

Six decisions are easier to make before anyone has a Bot running than after. Tick each one off as you settle it.

**Before you invite the team**

- [ ] **Privacy mode.** A team on Privacy Mode (Legacy) can't use Grok Bot at all. Change the setting in Team Settings first.
- [ ] **Plugins.** Check the team's plugin policy. Every plugin you allow is open to every Bot a member runs.
- [ ] **Members' own computers.** Set **Execution on Local Computer** to **Never allow** unless Bots have a reason to work on members' machines.
- [ ] **Spending.** Set the team's on-demand limit. On-demand starts on for Teams, and no cap covers Grok Bot alone.
- [ ] **Team Bots.** Agree which keys may go on one. A secret on a Team Bot is access for the whole team, so use read-only service keys, never a person's own.
- [ ] **Auto-review, on Enterprise.** Turn on **Enforce Auto-review** if Team Bots should be checked in teammates' chats and in Slack, where nobody is there to answer an approval card.

The dashboard's **Setup Checklist** then walks an admin through the rest: plugins, Slack or Microsoft Teams, GitHub, sign-in, network settings and inviting teammates. **Invite Team**, on the same page, emails members a download link.

## Check: who pays for this one?

Use the figure on one more case.

**Predict: Sam owns a Team Bot that's in the team's Slack. A teammate builds a Slack workflow that posts to a channel every hour and mentions the Bot. Whose usage does each hourly answer spend?**

- The teammate's, because the teammate built the workflow
- Sam's, because a workflow isn't a linked teammate
- Nobody's, because no person asked

Answer: Sam's, because a workflow isn't a linked teammate

A request spends the usage of the person who sent it. A post from a workflow has no linked person behind it, so it counts against the Bot's owner. An hourly workflow is 24 answers a day on Sam's usage, so Sam should know about it before it's switched on.

Rolling out to a team also means deciding which accounts Bots may touch.

**Next:** [Is it safe?](https://learngrokbot.com/safety)

A Bot acts as you on every account you sign it in to, and all your Bots share those logins. See what to connect first, what to leave out and how data is used.

### Does a member need a Premium seat for Grok Bot?

No. A Standard seat includes it. [Pricing](https://learngrokbot.com/pricing#plans) lists every plan that does.

### Can a member link a personal SuperGrok plan for more usage?

It adds nothing. On a Teams seat Grok Bot follows the seat, and a link doesn't add usage on top. Enterprise seats don't take a personal link at all.

### How is a Team Bot different from sharing a Bot as a template?

A template gives each person their own copy, which they then look after separately. A Team Bot is the same Bot for everyone: the owner maintains it, and a change reaches the whole team.

### Can I turn a Bot I already have into a Team Bot?

Yes. Open the Bot's share menu and choose **Publish to Team**. Grok Bot makes a separate team copy and asks what to bring across, and your own Bot stays private.

### Where does a Team Bot do its work?

In your own chat with it, usually on your own cloud computer, so it can use the files and logins there. In Slack channels, threads and group chats it works on one computer of its own. [The shared computer](https://learngrokbot.com/shared-computer) explains what lives on one.

### I'm not the owner. Why does it say "This Bot's owner has reached their usage limit"?

That message means the account paying for the chat has hit its limit. In your own chat with a teammate's Team Bot, that account is yours.

### Can I use a Team Bot on my phone?

Yes, for chatting. Team Bots you've added show up in the phone app. Creating, publishing and editing one, and connecting it to Slack, happen on a computer.

- 2026-10-06: First published.

## Sources

- [SpaceXAI docs: Grok Bot for teams and enterprises (who gets it, admin controls, before you roll out)](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [SpaceXAI docs: Team Bots (creating, publishing, usage, admins)](https://docs.x.ai/grok-bot/team-bots)
- [Cursor Help Center: Team Bots](https://cursor.com/help/grok-bot/team-bots)
- [Cursor docs: Grok Bot for Teams and Enterprise (Manage Team Bots, Enforce Auto-review)](https://cursor.com/docs/grok-bot/teams)
- [Cursor Help Center: Plans and billing (Teams seats, Enterprise, on-demand usage)](https://cursor.com/help/grok-bot/plans)
- [Cursor docs: Team pricing](https://cursor.com/docs/account/teams/pricing)
- [SpaceXAI: Team Bots announcement, 28 September 2026](https://x.ai/news/team-bots)
- [SpaceXAI: Grok Bot for enterprise, 3 September 2026](https://x.ai/news/grok-bot-for-enterprise)
- [SpaceXAI: Grok Bot changelog (v0.31.0, v0.55.0, v0.61.0, v0.62.0, v0.64.0)](https://x.ai/changelog/bot)
- [Grok on YouTube: Grok Bot 101, recorded on a Cursor Teams account (the New chat list and the rules list pictured)](https://www.youtube.com/watch?v=8xXhE25vJZY)
- [Riley Brown on YouTube (creating and publishing a Team Bot pictured)](https://www.youtube.com/watch?v=c9Z7ixVr4CU)