team-bots.md +0 −425 deleted
File Deleted View Diff
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 any managers, 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. The Bot checks what a copy would start from: this chat and its own
72 memories.
73 * If most of those memories are personal facts about you, such as your
74 family, health, or schedule, or the chat is about your own life or
75 individual work, it asks **How should your Team Bot start?** Choose
76 **Copy** *Bot name* to start with the Bot's chat and memories, or
77 **Start fresh** to create a new Team Bot without them.
78 * Otherwise, including when the Bot is new, it makes the copy right away and
79 replies **Done. Your team copy is in the sidebar.**
803. In the team copy's chat, work through the setup cards. For each one, choose
81 what the team copy gets: plugins, secrets, memories, skills, files, and
82 routines. Memories you don't pick stay private; choose **Keep private** to
83 share none.
844. For routines, choose whether each one moves to the team copy or stays on
85 your personal Bot. Either way, a routine only runs for you, and teammates
86 never see it.
87
88Your personal Bot stays private and keeps working for you, and teammates can't
89see the team copy until you publish it. If most of what a Bot knows is about
90you personally, a copy won't do much for your team. Create a new Team Bot
91instead.
92
93## Set up what the Bot needs
94
95The Bot's info pane shows a **Setup** section with cards for **Plugins**,
96**Secrets**, **Skills**, and **Files**. Each card shows what you added, or
97**None**. Choose a card to add to it or manage what it holds, or ask the Bot in
98chat. Only the owner and the Bot's [managers](#add-managers) can change this
99setup, and every change reaches all teammates.
100
101### Plugins
102
103Plugins you add to a Team Bot are shared: the Bot can use them in every
104conversation, including Slack channels and group chats, without asking anyone
105first. Each teammate still uses their own account where a plugin needs one, so
106how a plugin signs in decides whose access the Bot uses:
107
108| Plugin | Whose access the Bot uses | Required setup for teammates |
109| --- | --- | --- |
110| Signs in with an account (OAuth) | The person talking to the Bot | Each teammate connects their own account the first time they need it |
111| Configured with a key or token | The Bot's own credential, the same for everyone | None |
112| 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 |
113| 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 |
114
115For example, a Bot that reads Datadog alerts and files Linear tickets could
116use a Datadog plugin configured with a read-only key, so nobody signs in, and
117a Linear plugin that each teammate connects, so tickets are created by the
118person who asked.
119
120A **Command** server runs on whichever computer the conversation uses; see
121[Where the work runs](#where-the-work-runs). Teammates can use the shell on
122those computers and read the server's command and arguments, so never put a
123credential in either. A Command server that needs environment variables, or
124whose arguments look like a credential, runs only in your own chat. For a
125custom server that needs secrets, choose **Remote HTTPS**.
126
127Teammates can also bring their own connectors. A teammate who needs a service
128the Bot doesn't have can add it as a personal plugin from their own chat, and
129the Bot's shared plugins don't change. The Bot uses a person's own connectors
130in their 1:1 chat, in the app or a Slack DM, without asking. In a shared
131conversation, such as a Slack thread or a group chat, it asks that person
132first; see [Personal connectors and approvals](#personal-connectors-and-approvals).
133
134Your team's [connector policy](/grok-bot/teams-and-enterprises#connector-policy)
135applies to Team Bots the same way it applies to other Bots.
136
137### Secrets
138
139Add a secret when a plugin or a script the Bot runs needs a key that has no
140plugin sign-in. Each secret has a name, description, and value. Names use
141uppercase letters, digits, and underscores and start with a letter, such as
142`DATADOG_API_KEY`.
143
144* Values are encrypted when stored, and the app shows only each secret's name
145 and description. Teammates never see a value.
146* The Bot can't see a value either. It uses a secret by name, and the value is
147 replaced with `[REDACTED]` in the output of the commands it runs, the files it
148 reads, and its plugin calls.
149* The Bot can use every secret in any teammate's conversation, so treat a
150 secret as access you are giving the whole team.
151* Use scoped, read-only service-account keys instead of personal credentials.
152* A Team Bot holds up to 25 secrets. Each value is at least 8 characters, so
153 it can be redacted reliably, and at most 4,096 bytes.
154
155When the Bot needs a key it doesn't have, it sends a secret request in the
156owner's or a manager's own chat in the Grok Bot app. Any other teammate who
157needs one hears that the owner or a manager adds it.
158
159### Skills and files
160
161**Skills** are the team's repeatable how-tos: how to qualify a lead, how to
162triage an alert, how your team writes release notes. Add them from your skill
163library or write new ones. Each team skill applies in every teammate's
164conversation.
165
166**Files** give the Bot shared reference material, such as playbooks, FAQs, or
167schemas. Choose the **Files** card, then choose **Upload file** or drag files
168in. Supported formats are .txt, .md, .markdown, .csv, .json, .yaml, and .yml,
169up to 256,000 characters per file.
170
171Only the owner or a manager saves a team skill. When another teammate teaches
172the Bot a new process in their own chat, the Bot keeps it in its notes with that
173person and tells them the owner or a manager can make it a team how-to.
174
175### Memory
176
177A Team Bot keeps two kinds of memory:
178
179* **Team memory** is read by every teammate's conversation. The Bot saves a
180 fact there only when someone says the whole team should have it, and it
181 tells you when it does.
182* **Notes with each person** are private to that person. They hold that
183 person's preferences and context and follow them across their app chat and
184 Slack DMs with the Bot. No other teammate's conversation reads them.
185
186To see what the Bot has saved for the team, ask it in chat. To correct or
187remove something, tell it.
188
189## Publish a Team Bot
190
191When setup is done, the sidebar shows **You built a Bot. Now your whole team
192gets a teammate.** Choose **Publish to team**, or ask the Bot to publish.
193
194After you publish:
195
196* Teammates find the Bot under **New chat → Team Bots**.
197* Choose **Copy link** to send it to someone directly.
198* You can [add it to Slack](#add-a-team-bot-to-slack).
199
200To take the Bot away from teammates for a while, choose **Unpublish** in its
201details. Teammates lose access until you publish it again. Their chats and
202routines come back when you do.
203
204To change the Bot's **Name** or **Description**, edit them in the Bot's
205details; the description is under **About**. The description is up to 140 characters and is what teammates read
206when they find the Bot, so write it in the Bot's own voice: “I answer
207questions about our Datadog alerts.”
208
209### Add managers
210
211Once the Bot is published, you can make teammates its managers. In the Bot's
212details, the **Managers** section sits under **Setup**. Choose **Add**, pick a
213teammate, then choose **Add manager**. A manager can change the Bot's setup,
214like its profile, skills, plugins, secrets, and Slack app, and every change
215reaches the whole team. Publishing, unpublishing, and deleting the Bot stay
216with you.
217
218To remove a manager, choose the trash icon (**Remove manager**) next to their
219name, then **Remove**.
220
221## Use a Team Bot
222
2231. Choose **New chat**, then **Team Bots** at the bottom of it.
2242. Find the Bot. In the desktop app, type at least three characters in
225 **Search Team Bots** to search Bots you haven't added.
2263. Choose **Add**, then **Start a chat**.
227
228You can also open a link a teammate sends you. A Team Bot shows its owner's
229name next to its own.
230
231Your chat with a Team Bot is yours alone and starts fresh. The Bot knows what
232is saved on it for the team and what it has learned about you, not what other
233teammates said to it.
234
235As a teammate, you can pin a Team Bot, hide it from your sidebar, and set up
236your own routines with it. You can't delete it, and you can't change its setup
237unless the owner makes you a [manager](#add-managers). Ask the owner or a
238manager for changes to shared plugins, secrets, skills, or files.
239
240### Routines on a Team Bot
241
242Routines are personal. A routine belongs to whoever set it up with the Bot, in
243their own chat. It runs as them, reports in their chat, and only they can see
244or change it. No routine runs for the whole team at once.
245
246To give the whole team the output of a routine, have the routine post its
247result somewhere shared, such as a Slack channel. See
248[Skills, routines, and automations](/grok-bot/skills-routines-and-automations).
249
250## Where the work runs
251
252A Team Bot works on a Grok Bot computer, like any Bot. Which computer depends
253on the conversation:
254
255| Conversation | Computer |
256| --- | --- |
257| The owner's own chat | The owner's computer |
258| A teammate's chat in the app, or their 1:1 Slack DM with the Bot | That teammate's own computer |
259| Slack channels, group DMs, and threads | One shared computer for that Bot, separate from the owner's and every teammate's |
260
261Files you upload in your own chat land on your computer, not the owner's.
262Because Slack channel conversations share one computer, don't share anything
263in a channel thread that shouldn't be visible to everyone in that channel.
264
265## Personal connectors and approvals
266
267In a shared conversation, such as a Slack thread or a group chat, a Team Bot
268asks before it uses one of your own connectors. Plugins on the Bot don't need
269this, and neither does your 1:1 chat with the Bot. The card reads **Allow** and
270the plugin's name, and says which account it will use:
271
272* **Allow once** lets the Bot use it for this reply and your next message,
273 unless someone else writes in between.
274* **Always allow for this Bot** remembers your answer for this Team Bot.
275* **Always allow for all Team Bots** remembers your answer for every Team Bot
276 on your team.
277* **Skip** leaves the plugin unused for this reply.
278
279If you haven't connected the plugin yet, the Bot asks you to sign in. In
280Slack, it sends you a sign-in link.
281
282To undo remembered answers, go to **Settings → General → Team Bots** and choose
283**Clear**. Team Bots ask again the next time they need one of your connectors.
284
285The rest of the approval model, including Auto-review, applies to Team Bots as
286it does to every Bot, with one difference. In a conversation where nobody can
287answer an approval card, the Bot runs without Auto-review and stays within the
288permissions it was set up with, unless your team requires Auto-review. See
289[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy).
290
291## Add a Team Bot to Slack
292
293A published Team Bot can have its own Slack app, named after the Bot and using
294its avatar. Teammates can DM it or @mention it in channels, and it answers
295with the same plugins, context, and memories it has in the Grok Bot app. It
296posts as itself, not as the owner.
297
298The owner adds a Team Bot to Slack, and the Bot must be published first. A
299[manager](#add-managers) can add it too. The setup then uses the owner's Slack
300connection, so the owner connects Slack first.
301
3021. In the Bot's details, choose **Bring to your team's Slack**.
3032. Choose **Connect Slack workspace** and approve Cursor in the Slack page
304 that opens.
3053. Pick the workspace and choose **Connect**. Pick a workspace you can install
306 apps in.
3074. Grok Bot creates the Slack app and installs it. The Bot sends you a welcome
308 DM in Slack when it is ready.
3095. Invite the Bot to the channels where it should work, for example with
310 `/invite @BotName`.
311
312Each Team Bot is its own Slack app, separate from the Cursor app in Slack.
313
314### Slack admin approval
315
316If your Slack workspace requires approval for new apps, choosing **Connect**
317opens Slack's approval request page, where you submit the request. Once Slack
318has it, the setup shows **Awaiting admin approval** and the date you last
319submitted. Choose **Check approval** once an admin approves, **Resubmit** to
320open Slack's request page again, or **Cancel request** to stop the install.
321
322If an admin denied the last request, the setup shows when, and choosing
323**Connect** again starts a new request.
324
325Slack admins can approve Team Bots automatically with Slack's app-approval
326automations. See [How to set it up](https://cursor.com/bot/slack-auto-approve).
327
328If Slack asks an admin to approve Cursor itself, the admin approves it, and
329then you connect again.
330
331### How the Bot behaves in Slack
332
333* **Direct messages:** the Bot answers every message. A DM is one conversation.
334* **Channels and group DMs:** the Bot answers when someone @mentions it in a
335 conversation it has been added to. After that, it follows the thread, so
336 later replies wake it without another mention. Each thread is its own
337 conversation.
338* **Other channel messages:** the Bot ignores top-level messages that don't
339 mention it. Use a Slack channel listener routine to have it respond to every
340 message in a channel.
341
342### Link your Slack account
343
344The Bot answers only people who have linked their Slack account to Cursor, so
345it knows who is asking and whose accounts to use. Posts from Slack workflows
346and other apps are the exception; see [Usage](#usage). Each teammate links once
347under **Settings → General → Team Bots**. When someone who hasn't linked
348messages the Bot, it shows them a private **Link Account** button and posts a
349short reminder in the thread pointing to it.
350
351If a linked account isn't on the Bot's Cursor team, the Bot tells that person
352privately and doesn't answer.
353
354Unlinking stops Team Bots, and Cloud Agents started from Slack, from answering
355you there until you link again.
356
357### Remove a Team Bot from Slack
358
359In the Bot's details, choose **Remove from Slack**. This deletes the app from
360the Slack workspace, and teammates can't reach the Bot from Slack until you
361add it again. The Team Bot keeps working in the Grok Bot app.
362
363## Usage
364
365When a teammate talks to a Team Bot, in the app or in Slack, the usage counts
366against that teammate's own Grok Bot allowance, not the owner's. A routine
367counts against the allowance of the person who set it up. Messages in Slack
368that don't come from a linked teammate, such as posts from a Slack workflow,
369count against the owner.
370
371If a teammate is out of usage, the Bot tells them in the chat or Slack thread
372instead of using the owner's. See
373[Plans and billing](https://cursor.com/help/grok-bot/plans).
374
375## For admins
376
377Team Bots follow the same team controls as every Bot, including your connector
378policy, Team Rules, and Auto-review settings. See
379[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).
380
381### Add Team Bots for members by default
382
383On the Grok Bot page of the
384[Cursor dashboard](https://cursor.com/dashboard/bot), under **Team Bots**,
385choose **Manage Team Bots**. For each Team Bot, choose who gets it in their
386sidebar automatically: **All team**, **None**, or specific groups. Groups come
387from the **Members & Groups** page.
388
389Members who get a Team Bot this way see **Required by your admin. You can't
390turn this off.**
391
392Admins choose who gets a Team Bot by default. Only the Bot's owner and its
393managers change its plugins, secrets, skills, and files.
394
395### Delete a Team Bot as an admin
396
397In **Manage Team Bots**, choose the trash icon on the Bot's row. Type the Bot's
398exact name to confirm, then choose **Delete**. The Bot is deleted for everyone
399on your team, and its Slack app is removed from Slack. If the Slack app can't be
400removed, a Slack workspace admin can remove it in Slack.
401
402### Audit logs
403
404On Enterprise, [audit logs](/grok-bot/teams-and-enterprises#audit-logs) record
405Team Bot events, including when a Bot is created, published, unpublished, or
406deleted, changes to its skills, and Slack account links.
407
408## Delete a Team Bot
409
410The owner can delete a Team Bot, and so can a team admin from
411[Manage Team Bots](#delete-a-team-bot-as-an-admin). Deleting it removes the Bot
412for your whole team: teammates lose it, along with their chats and routines on
413it. This can't be undone.
414
415If you may need the Bot again, choose **Unpublish** instead.
416
417## Related pages
418
419* [Create and manage Bots](/grok-bot/bots)
420* [Message and collaborate](/grok-bot/chat-and-collaboration)
421* [Use the computer and apps](/grok-bot/computer-and-apps)
422* [Skills, routines, and automations](/grok-bot/skills-routines-and-automations)
423* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)
424* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)
425* [Troubleshooting](/grok-bot/troubleshooting)