Grok Bot Team Bots: Sharing, Slack, Privacy and Admin Controls

Team Bots are for members of a Cursor team who have Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition.. The quickest check is the command palette: press ⌘+K on Mac or Ctrl+K on Windows and Linux and look for Create new Team Bot. If it is missing, either you are not on a Cursor team or your Grok Bot app needs an update.

A Team Bot is a Bot one person owns and shares with the team. The owner decides who can chat with it, everyone on the team or only certain people and groups. Team Bots always run in the cloud, so a Bot that runs on your own computer cannot become one, and your personal Bots stay exactly as they were.

Cursor's Teams and Enterprise docs call Team Bots the exception to one Bot per user, which is why most of this page is about who gets what once several people share one.

There are two routes. You can start a fresh Team Bot from the command palette, or make a team copy of a Bot you already rely on. The fresh route looks like this.

1. 1Open the command palette (⌘+K or Ctrl+K) and choose Create new Team Bot. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. creates a Bot named New Team Bot and opens its chat.
2. 2Tell the Bot what it should help the team with. A sentence is enough.
3. 3Follow its setup steps for apps, secrets and skills, then files. Add only keys and files the whole team may use.
4. 4Click the Bot's name at the top of the chat to rename it, and edit the description under About.
5. 5Share it from the ready card or from Share in the Bot's details.

Step four is easy to skip and it blocks everything after it. Until the Bot has a name or a description, its details say Draft · Only you can see it, teammates cannot find it, and Share does not appear.

To convert a Bot you already have, click its name, open Share and choose Share with your Team. The Bot makes a separate team copy of itself and walks you through what to bring: apps, secrets, skills, memories and routines, then files. It shows which of its memories the team should have, and you pick Share with team or Keep private. Routines can move to the team copy or stay on the personal Bot.

The personal Bot keeps working and its chats do not move. The team copy sits in your sidebar, hidden from teammates until you share it, and connects to Slack as its own app with its own handle. Of all the setup steps, secrets is the one I would slow down on. Cursor's docs say secrets, apps and files the owner or a Manager adds are available in every teammate's chat, so a key you bring across is a key the team can use.

Sharing and publishing are the same act here. When the Bot is ready it shows a card saying so, and Publish to team shares it with everyone on the team. After that the card offers Copy link. Sharing with anyone at all also publishes the Bot.

For narrower access, click the Bot's name and choose Share. In Share this Bot, Who has access takes either your team or People you invite, and limiting it asks you to confirm with Limit access. Add people or groups then asks which role each person gets under Add as.

Teammates have three ways in. The command palette has a Team Bots list that shows Bots shared with them and who made each one, with Add to keep a Bot in the sidebar. On the phone, search has a Team Bots option. And a link a teammate sends opens the Bot with Start a chat. To get that link, right-click the Bot in the sidebar and choose Copy link.

Each person's chat with a Team Bot is private. The owner and Managers cannot read yours, and you cannot read theirs. The Bot can save things it learns for the whole team and tells you when it does, but it does not save anything about you personally for the team. What it remembers about working with you stays between you and the Bot.

Everything else depends on where the conversation happens. Your own chat in the app behaves one way, and the shared places (Slack channels, threads, group DMs and group chats) behave another.

The apps row comes with a prompt. When the Bot wants one of your personal accounts, the card says Allow followed by the app name, with Allow once, Always allow and Skip. Always allow has two scopes in its menu: your messages to this Bot, or your messages to every Team Bot. A connected account always acts as the person the Bot is answering, so one teammate's connection is never used for someone else. To make every Team Bot ask again, open Settings > General > Team Bots and choose Clear next to Clear connector preferences.

The computer row has an exception. Sometimes the Bot uses a separate computer just for that conversation, for example when your privacy mode is stricter than the owner's. When it does use your computer, it can use the files there and the sites you are signed in to, which is worth knowing before you sign in to anything on it.

Usage follows the person being answered, so your own limits apply in your chat, in Slack and in group chats. The owner's usage pays for the owner's own messages and for Slack posts from apps or workflows not linked to a Cursor account. Plan and limit details are on Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. pricing.

A Team Bot asks the person it is answering before risky actions. In a Slack thread it posts a Review an action card with Allow once, Deny and View details, and only the person who asked can answer. The general approval model is on Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. approvals. One admin detail belongs here, though: in chats where nobody can answer an approval, Team Bots otherwise run without Auto-review, and the Enterprise Enforce Auto-review switch is what makes them check risky actions there too.

Adding a Team Bot to Slack happens after sharing, and only the owner or a Manager can do it.

1. 1Click the Bot's name at the top of the chat.
2. 2Find Bring to your team's Slack and choose Connect. Before publishing, the row reads Slack with Connect after publishing.
3. 3If it says Awaiting admin approval, a Slack workspace admin needs to approve the app.
4. 4Once it says Connected, teammates can message the Bot directly or mention it in channels.

Each teammate links their Slack account first, under Settings > General > Team Bots with Link, using the Cursor account on the Bot's team. Anyone who messages the Bot before linking gets a reply with the steps.

Slack is also where a Team Bot can do something a personal Bot cannot. In a channel thread or DM it acts for the teammate who mentioned it, so it can hand work to that person's own Bots, and their replies come back into the same thread. A personal Bot does not hand work to other Bots from a channel thread. Bots record who asked for each message they post, so anyone in the thread can ask who requested it, and when a Team Bot's routine replies in a thread, the Bot follows that thread and answers later replies without an @mention.

Yes to all three, with limits. On the phone you can chat with Team Bots you have added, find others through search and Team Bots, and answer their Allow cards. A Team Bot cannot be your primary Bot, and creating, sharing, editing and connecting to Slack all stay on desktop.

Voice chat with a teammate's Team Bot works on desktop, from your own chat with it, with Start voice chat. A published Team Bot can also join your own group chat, as long as the group has no Bots that run on your own computer. Both features are covered on group chats and voice.

The owner and the Bot's Managers can change a Team Bot from its details. Plugins (its connected apps), Secrets, Skills and Files hold what the Bot uses for everyone. The name and the About description are edited in place, and Share controls who can use it and who manages it.

Two actions belong to the owner alone. Unpublish, in the Bot's details, hides it from teammates until it is shared again. Delete, from right-clicking the Bot in the sidebar, removes it for the whole team along with teammates' chats and routines on it, and it cannot be undone. If you only want a Team Bot out of your own sidebar, Hide from sidebar does that, and Add in the Team Bots list brings it back.

Admins have their own view. On the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. page of the Cursor dashboard, Manage Team Bots under Team Bots lists every Team Bot with two controls.

Admins can delete a Team Bot from the same page, which removes it for everyone, removes its Slack app, and cannot be undone. The wider admin controls, including public template sharing (off by default on Enterprise, allowed by default on other teams), are on Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. for Teams and Enterprise.

Most of these come down to sharing state or account access, and the messages are specific enough to diagnose from. The table maps what you see to what it means.

The two usage rows look alike and point at different people, which is the part that trips teammates up. One means your usage ran out; the other means that particular reply was billed to the owner, so the owner needs to check their plan. If nothing in the table matches, contact Cursor support with the Bot's name, the exact message and your Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. version.