1#### Work with Grok Bot
2
3# Team Bots
4
5A Team Bot is one Bot that your whole team talks to. Its owner sets it up once,
6with the plugins, secrets, skills, and files it needs, and publishes it to the
7team. Every teammate can then chat with it in the Grok Bot app or in Slack
8without starting from scratch.
9
10## Why use Team Bots?
11
12A Bot becomes useful as you teach it: the tools it can reach, the way your team
13works, and the details it keeps getting wrong. On a personal Bot, that work
14helps one person. A Team Bot shares it:
15
16* **You set it up once, and everyone uses it.** The plugins, secrets, skills, and files
17 the owner adds are available in every teammate's conversation.
18* **It learns from the team.** When someone tells the Bot something the whole
19 team should know, it saves it to team memory, which every teammate's
20 conversation reads.
21* **Every conversation stays private.** Each teammate gets their own chat. The
22 owner can't read teammates' chats, and teammates can't read the owner's.
23* **It acts as the person asking.** A plugin that needs a sign-in uses the
24 account of whoever is talking to the Bot. A Team Bot never lends one
25 person's access to another.
26* **It can have its own Slack app.** Teammates DM it or @mention it, and it
27 posts as itself.
28
29Team Bots suit one shared job, such as answering metrics questions from your
30data warehouse, keeping docs current as PRs ship, triaging requests posted in
31a Slack channel, or answering internal helpdesk questions from a knowledge
32base. For an everyday assistant that works from your own accounts and
33memories, keep a personal Bot.
34
35### Team Bots, personal Bots, and public templates
36
37| | Personal Bot | Public template | Team Bot |
38| --- | --- | --- | --- |
39| Who talks to it | Only you | Each person who adds it talks to their own copy | Everyone on your team, each in their own chat |
40| Who maintains it | You | Each copy's new owner, separately | The owner, and changes reach everyone |
41| Memory | Yours | Starts from what the template shares, then separate per copy | Team memory, plus private notes with each person |
42
43## How to access
44
45Team Bots are available to members of a team. Create, set up, and
46publish them in the Grok Bot desktop app. Teammates can use a published Team
47Bot from the desktop app, the [mobile app](/grok-bot/mobile), and Slack.
48
49If your account can't use Team Bots, opening a Team Bot link shows **Team Bots
50Not Available**.
51
52## Create a Team Bot
53
541. Choose **New chat** in the sidebar or press `Cmd/Ctrl+N`.
552. In **New chat**, choose **Create new Team Bot**.
563. The Bot opens its own chat, asks what the team needs it for, and walks you
57 through plugins, secrets, skills, and files.
584. Give it a concrete job and try it on real tasks. Correct it as you go.
59
60Until you [publish it](#publish-a-team-bot), only you can see the Team Bot.
61Each teammate who opens it later gets their own chat. That chat starts
62without this conversation and includes the plugins, secrets, skills, files,
63and memory you saved for the team.
64
65### Start from a Bot you already have
66
67If a personal Bot already does work the team would share, make a team copy of
68it:
69
701. Open the Bot's **Share** menu and choose **Publish to Team**.
712. In **How should your Team Bot start?**, choose one:
72 * **Copy** *Bot name* to start with the Bot's chat and memories. Your
73 personal Bot stays private and keeps working for you.
74 * **Start fresh** to create a new Team Bot without the chat or its memories.
753. Work through the setup cards. For each one, choose what the team copy gets:
76 plugins, secrets, memories, skills, files, and routines. Memories you don't
77 pick stay private; choose **Keep private** to share none.
784. For routines, choose whether each one moves to the team copy or stays on
79 your personal Bot. Either way, a routine only runs for you, and teammates
80 never see it.
81
82If most of what a Bot knows is about you personally, a copy won't do much for
83your team. Create a new Team Bot instead.
84
85## Set up what the Bot needs
86
87The Bot's info pane shows a **Setup** section with **Plugins**, **Secrets**,
88**Skills**, and **Files**. Choose **Add** on any row, or ask the Bot in chat.
89Only the owner can change this setup, and every change reaches all teammates.
90
91### Plugins
92
93Plugins you add to a Team Bot are shared: the Bot can use them in every
94conversation, including Slack channels and group chats, without asking anyone
95first. Each teammate still uses their own account where a plugin needs one, so
96how a plugin signs in decides whose access the Bot uses:
97
98| Plugin | Whose access the Bot uses | Required setup for teammates |
99| --- | --- | --- |
100| Signs in with an account (OAuth) | The person talking to the Bot | Each teammate connects their own account the first time they need it |
101| Configured with a key or token | The Bot's own credential, the same for everyone | None |
102| Custom MCP server, **Remote HTTPS** | The Bot's own credential, or each person's sign-in if the server uses OAuth | None, or a one-time sign-in |
103| Custom MCP server, **Command** | Runs on the computer each conversation uses | None. A command that needs secrets works only in the owner's own chat |
104
105For example, a Bot that reads Datadog alerts and files Linear tickets could
106use a Datadog plugin configured with a read-only key, so nobody signs in, and
107a Linear plugin that each teammate connects, so tickets are created by the
108person who asked.
109
110A **Command** server runs on whichever computer the conversation uses; see
111[Where the work runs](#where-the-work-runs). Teammates can use the shell on
112those computers and read the server's command and arguments, so never put a
113credential in either. A Command server that needs environment variables, or
114whose arguments look like a credential, runs only in your own chat. For a
115custom server that needs secrets, choose **Remote HTTPS**.
116
117Teammates can also bring their own connectors. A teammate who needs a service
118the Bot doesn't have can add it as a personal plugin from their own chat, and
119the Bot's shared plugins don't change. The Bot uses a person's own connectors
120in their 1:1 chat, in the app or a Slack DM, without asking. In a shared
121conversation, such as a Slack thread or a group chat, it asks that person
122first; see [Personal connectors and approvals](#personal-connectors-and-approvals).
123
124Your team's [connector policy](/grok-bot/teams-and-enterprises#connector-policy)
125applies to Team Bots the same way it applies to other Bots.
126
127### Secrets
128
129Add a secret when a plugin or a script the Bot runs needs a key that has no
130plugin sign-in. Each secret has a name, description, and value. Names use
131uppercase letters, digits, and underscores and start with a letter, such as
132`DATADOG_API_KEY`.
133
134* Values are encrypted when stored, and the app shows only each secret's name
135 and description. Teammates never see a value.
136* The Bot can't see a value either. It uses a secret by name, and the value is
137 replaced with `[REDACTED]` in the output of the commands it runs, the files it
138 reads, and its plugin calls.
139* The Bot can use every secret in any teammate's conversation, so treat a
140 secret as access you are giving the whole team.
141* Use scoped, read-only service-account keys instead of personal credentials.
142* A Team Bot holds up to 25 secrets. Each value is at least 8 characters, so
143 it can be redacted reliably, and at most 4,096 bytes.
144
145When the Bot needs a key it doesn't have, it asks the owner with a secret
146request in the owner's chat. A teammate who needs one hears that the owner
147adds it.
148
149### Skills and files
150
151**Skills** are the team's repeatable how-tos: how to qualify a lead, how to
152triage an alert, how your team writes release notes. Add them from your skill
153library or write new ones. Each team skill applies in every teammate's
154conversation.
155
156**Files** give the Bot shared reference material, such as playbooks, FAQs, or
157schemas. Choose **Add** on the Files row, then choose **Upload file** or drag
158files in. Supported formats are .txt, .md, .markdown, .csv, .json, .yaml, and
159.yml, up to 256,000 characters per file.
160
161Only the owner saves a team skill. When a teammate teaches the Bot a new
162process in their own chat, the Bot keeps it in its notes with that person and
163tells them the owner can make it a team how-to.
164
165### Memory
166
167A Team Bot keeps two kinds of memory:
168
169* **Team memory** is read by every teammate's conversation. The Bot saves a
170 fact there only when someone says the whole team should have it, and it
171 tells you when it does.
172* **Notes with each person** are private to that person. They hold that
173 person's preferences and context and follow them across their app chat and
174 Slack DMs with the Bot. No other teammate's conversation reads them.
175
176To see what the Bot has saved for the team, ask it in chat. To correct or
177remove something, tell it.
178
179## Publish a Team Bot
180
181When setup is done, the sidebar shows **You built a Bot. Now your whole team
182gets a teammate.** Choose **Publish to team**, or ask the Bot to publish.
183
184After you publish:
185
186* Teammates find the Bot under **New chat → Team Bots**.
187* Choose **Copy link** to send it to someone directly.
188* You can [add it to Slack](#add-a-team-bot-to-slack).
189
190To take the Bot away from teammates for a while, choose **Unpublish** in its
191details. Teammates lose access until you publish it again. Their chats and
192routines come back when you do.
193
194To change the Bot's **Name** or **Description**, edit them in the Bot's
195details. The description is up to 140 characters and is what teammates read
196when they find the Bot, so write it in the Bot's own voice: “I answer
197questions about our Datadog alerts.”
198
199## Use a Team Bot
200
2011. Choose **New chat**, then **Team Bots** at the bottom of it.
2022. Find the Bot. In the desktop app, type at least three characters in
203 **Search Team Bots** to search Bots you haven't added.
2043. Choose **Add**, then **Start a chat**.
205
206You can also open a link a teammate sends you. A Team Bot shows its owner's
207name next to its own.
208
209Your chat with a Team Bot is yours alone and starts fresh. The Bot knows what
210is saved on it for the team and what it has learned about you, not what other
211teammates said to it.
212
213As a teammate, you can pin a Team Bot, hide it from your sidebar, and set up
214your own routines with it. You can't change its setup or delete it. Ask the
215owner for changes to shared plugins, secrets, skills, or files.
216
217### Routines on a Team Bot
218
219Routines are personal. A routine belongs to whoever set it up with the Bot, in
220their own chat. It runs as them, reports in their chat, and only they can see
221or change it. No routine runs for the whole team at once.
222
223To give the whole team the output of a routine, have the routine post its
224result somewhere shared, such as a Slack channel. See
225[Skills, routines, and automations](/grok-bot/skills-routines-and-automations).
226
227## Where the work runs
228
229A Team Bot works on a Grok Bot computer, like any Bot. Which computer depends
230on the conversation:
231
232| Conversation | Computer |
233| --- | --- |
234| The owner's own chat | The owner's computer |
235| A teammate's chat in the app, or their 1:1 Slack DM with the Bot | That teammate's own computer |
236| Slack channels, group DMs, and threads | One shared computer for that Bot, separate from the owner's and every teammate's |
237
238Files you upload in your own chat land on your computer, not the owner's.
239Because Slack channel conversations share one computer, don't share anything
240in a channel thread that shouldn't be visible to everyone in that channel.
241
242## Personal connectors and approvals
243
244In a shared conversation, such as a Slack thread or a group chat, a Team Bot
245asks before it uses one of your own connectors. Plugins on the Bot don't need
246this, and neither does your 1:1 chat with the Bot. The card reads **Allow** and
247the plugin's name, and says which account it will use:
248
249* **Allow once** lets the Bot use it for this reply.
250* **Always allow for this Bot** remembers your answer for this Team Bot.
251* **Always allow for all Team Bots** remembers your answer for every Team Bot
252 on your team.
253* **Skip** leaves the plugin unused for this reply.
254
255If you haven't connected the plugin yet, the Bot asks you to sign in. In
256Slack, it sends you a sign-in link.
257
258To undo remembered answers, go to **Settings → General → Team Bots** and choose
259**Clear**. Team Bots ask again the next time they need one of your connectors.
260
261The rest of the approval model, including Auto-review, applies to Team Bots as
262it does to every Bot, with one difference. In a conversation where nobody can
263answer an approval card, the Bot runs without Auto-review and stays within the
264permissions it was set up with, unless your team requires Auto-review. See
265[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy).
266
267## Add a Team Bot to Slack
268
269A published Team Bot can have its own Slack app, named after the Bot and using
270its avatar. Teammates can DM it or @mention it in channels, and it answers
271with the same plugins, context, and memories it has in the Grok Bot app. It
272posts as itself, not as the owner.
273
274Only the owner adds a Team Bot to Slack, and the Bot must be published first.
275
2761. In the Bot's details, choose **Bring to your team's Slack**.
2772. Choose **Connect Slack workspace** and approve Cursor in the Slack page
278 that opens.
2793. Pick the workspace and choose **Connect**. Pick a workspace you can install
280 apps in.
2814. Grok Bot creates the Slack app and installs it. The Bot sends you a welcome
282 DM in Slack when it is ready.
2835. Invite the Bot to the channels where it should work, for example with
284 `/invite @BotName`.
285
286Each Team Bot is its own Slack app, separate from the Cursor app in Slack.
287
288### Slack admin approval
289
290If your Slack workspace requires approval for new apps, the setup shows
291**Awaiting admin approval**. Choose **Send request in Slack** to file the
292request, then **Check approval** once an admin approves. **Cancel setup**
293before you send the request, or **Cancel request** after, stops the install.
294
295Slack admins can approve Team Bots automatically with Slack's app-approval
296automations. See [How to set it up](https://cursor.com/bot/slack-auto-approve).
297
298If Slack asks an admin to approve Cursor itself, the admin approves it, and
299then you connect again.
300
301### How the Bot behaves in Slack
302
303* **Direct messages:** the Bot answers every message. A DM is one conversation.
304* **Channels and group DMs:** the Bot answers when someone @mentions it in a
305 conversation it has been added to. After that, it follows the thread, so
306 later replies wake it without another mention. Each thread is its own
307 conversation.
308* **Other channel messages:** the Bot ignores top-level messages that don't
309 mention it. Use a Slack channel listener routine to have it respond to every
310 message in a channel.
311
312### Link your Slack account
313
314The Bot answers only people who have linked their Slack account to Cursor, so
315it knows who is asking and whose accounts to use. Posts from Slack workflows
316and other apps are the exception; see [Usage](#usage). Each teammate links once
317under **Settings → General → Team Bots**. When someone who hasn't linked
318messages the Bot, it shows them a private **Link Account** button and posts a
319short reminder in the thread pointing to it.
320
321If a linked account isn't on the Bot's Cursor team, the Bot tells that person
322privately and doesn't answer.
323
324Unlinking stops Team Bots, and Cloud Agents started from Slack, from answering
325you there until you link again.
326
327### Remove a Team Bot from Slack
328
329In the Bot's details, choose **Remove from Slack**. This deletes the app from
330the Slack workspace, and teammates can't reach the Bot from Slack until you
331add it again. The Team Bot keeps working in the Grok Bot app.
332
333## Usage
334
335When a teammate talks to a Team Bot, in the app or in Slack, the usage counts
336against that teammate's own Grok Bot allowance, not the owner's. A routine
337counts against the allowance of the person who set it up. Messages in Slack
338that don't come from a linked teammate, such as posts from a Slack workflow,
339count against the owner.
340
341If a teammate is out of usage, the Bot tells them in the chat or Slack thread
342instead of using the owner's. See
343[Plans and billing](https://cursor.com/help/grok-bot/plans).
344
345## For admins
346
347Team Bots follow the same team controls as every Bot, including your connector
348policy, Team Rules, and Auto-review settings. See
349[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).
350
351### Add Team Bots for members by default
352
353On the Grok Bot page of the
354[Cursor dashboard](https://cursor.com/dashboard/bot), under **Bot
355Capabilities**, choose **Manage Team Bots**. For each Team Bot, choose who gets
356it in their sidebar automatically: **All team**, **None**, or specific groups.
357Groups come from the **Members & Groups** page.
358
359Members who get a Team Bot this way see **Required by your admin. You can't
360turn this off.**
361
362Admins choose who gets a Team Bot by default. Only the Bot's owner changes its
363plugins, secrets, skills, and files.
364
365### Audit logs
366
367On Enterprise, [audit logs](/grok-bot/teams-and-enterprises#audit-logs) record
368Team Bot events, including when a Bot is created, published, unpublished, or
369deleted, changes to its skills, and Slack account links.
370
371## Delete a Team Bot
372
373Only the owner can delete a Team Bot. Deleting it removes the Bot for your
374whole team: teammates lose it, along with their chats and routines on it. This
375can't be undone.
376
377If you may need the Bot again, choose **Unpublish** instead.
378
379## Related pages
380
381* [Create and manage Bots](/grok-bot/bots)
382* [Message and collaborate](/grok-bot/chat-and-collaboration)
383* [Use the computer and apps](/grok-bot/computer-and-apps)
384* [Skills, routines, and automations](/grok-bot/skills-routines-and-automations)
385* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)
386* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)
387* [Troubleshooting](/grok-bot/troubleshooting)
