SpyBara
Go Premium

Documentation 2026-11-10 23:57 UTC to 2026-11-11 23:00 UTC

16 files changed +796 −359. View all changes and history on the product overview
2026
Thu 12 22:57 Wed 11 23:00 Tue 10 23:57 Fri 6 23:59 Wed 4 23:01
Details

84 84 

85### Shared Bots and group chats85### Shared Bots and group chats

86 86 

87On a [shared Bot](/grok-bot/shared-bots), each teammate answers cards for their87On a [shared Bot](/grok-bot/team-bots), each teammate answers cards for their

88own requests in their own chat with the Bot. In a Slack thread, the card has88own requests in their own chat with the Bot. In a Slack thread, the card has

89**Allow once**, **Deny**, and **View details**, and only the person who asked89**Allow once**, **Deny**, and **View details**, and only the person who asked

90can answer. In a group chat, only the person whose message the Bot is answering90can answer. In a group chat, only the person whose message the Bot is answering


231URLs in a Bot you share. See [Share a Bot](/grok-bot/bots#share-a-bot) and the231URLs in a Bot you share. See [Share a Bot](/grok-bot/bots#share-a-bot) and the

232[third-party bot terms](https://x.ai/legal/bot-sharing-terms).232[third-party bot terms](https://x.ai/legal/bot-sharing-terms).

233 233 

234A [shared Bot](/grok-bot/shared-bots) is different: teammates chat with the same234A [shared Bot](/grok-bot/team-bots) is different: teammates chat with the same

235Bot, and the apps, secrets, skills, and files its owner adds work in every235Bot, and the apps, secrets, skills, and files its owner adds work in every

236teammate's chat. Only add keys and files you're happy for everyone you share it236teammate's chat. Only add keys and files you're happy for everyone you share it

237with to use.237with to use.

bots.md +10 −9

Details

36 36 

37To pick a different one later, right-click your primary Bot in the sidebar and37To pick a different one later, right-click your primary Bot in the sidebar and

38choose **Replace with different Bot**. On iPhone and Android, use **Replace38choose **Replace with different Bot**. On iPhone and Android, use **Replace

39Primary Bot…** in the Bot's menu. A [shared Bot](/grok-bot/shared-bots) can't39Primary Bot…** in the Bot's menu. A [shared Bot](/grok-bot/team-bots) can't

40be your primary Bot.40be your primary Bot.

41 41 

42## Edit a Bot42## Edit a Bot


51 51 

52The Bot keeps lasting rules in its memory. Personal Bots no longer have a52The Bot keeps lasting rules in its memory. Personal Bots no longer have a

53description or a **Bot settings** page; to change what a Bot does, tell it in53description or a **Bot settings** page; to change what a Bot does, tell it in

54chat. A [shared Bot](/grok-bot/shared-bots) still has a description, which its54chat. A [shared Bot](/grok-bot/team-bots) still has a description, which its

55owner or a Manager edits under **About** in the Bot's details.55owner or a Manager edits under **About** in the Bot's details.

56 56 

57### Change a Bot's name, picture, and label57### Change a Bot's name, picture, and label


133Adding a shared template creates a copy on the recipient's account. They never133Adding a shared template creates a copy on the recipient's account. They never

134get your computer, logins, or conversation history. To give your team one Bot134get your computer, logins, or conversation history. To give your team one Bot

135to chat with instead of a copy each, [share the Bot135to chat with instead of a copy each, [share the Bot

136itself](/grok-bot/shared-bots).136itself](/grok-bot/team-bots).

137 137 

138Shared templates are created by other users, not by Grok Bot. Adding one138Shared templates are created by other users, not by Grok Bot. Adding one

139accepts the [third-party bot terms](https://x.ai/legal/bot-sharing-terms) shown139accepts the [third-party bot terms](https://x.ai/legal/bot-sharing-terms) shown


223 223 

224### Who can see or change memory224### Who can see or change memory

225 225 

226A personal Bot's memory is yours, and only you can change it. A [shared226A personal Bot's memory is yours, and only you can change it. A [Team

227Bot](/grok-bot/shared-bots) can save things it learns for the whole team, and227Bot](/grok-bot/team-bots) can learn things for the whole team, and the owner

228it tells you when it does. It doesn't save anything about you personally for228or a Manager approves what it learns from teammates. It doesn't save anything

229the team; what it remembers about working with you stays between you and the229about you personally for the team; what it remembers about working with you

230Bot. A teammate's shared Bot doesn't get the facts your own Bots share about230stays between you and the Bot. A teammate's Team Bot doesn't get the facts your

231you.231own Bots share about you. See [What does a Team Bot learn for the

232team?](/grok-bot/team-bots#what-does-a-team-bot-learn-for-the-team)

232 233 

233### Import memory from another assistant234### Import memory from another assistant

234 235 

Details

67 67 

68Voice chat works with one Bot at a time, not in group chats; open that Bot's68Voice chat works with one Bot at a time, not in group chats; open that Bot's

69own chat to start a call. On desktop you can also voice chat with a teammate's69own chat to start a call. On desktop you can also voice chat with a teammate's

70[shared Bot](/grok-bot/shared-bots) from your own chat with it.70[shared Bot](/grok-bot/team-bots) from your own chat with it.

71 71 

72If the connection drops, Grok Bot tries to reconnect on its own first, so a72If the connection drops, Grok Bot tries to reconnect on its own first, so a

73short drop usually picks back up without you doing anything. If it can't, the73short drop usually picks back up without you doing anything. If it can't, the


217## Start a group chat217## Start a group chat

218 218 

219Use a group when several Bots need one shared outcome and visible handoffs.219Use a group when several Bots need one shared outcome and visible handoffs.

220You can also add a Bot a teammate [shared with you](/grok-bot/shared-bots), but220You can also add a Bot a teammate [shared with you](/grok-bot/team-bots), but

221not alongside Bots that run on your own computer.221not alongside Bots that run on your own computer.

222 222 

2231. Choose **New chat**, press `Cmd/Ctrl+Shift+N`, or open the command palette2231. Choose **New chat**, press `Cmd/Ctrl+Shift+N`, or open the command palette


301and noisy updates.301and noisy updates.

302 302 

303A handoff needs a Bot acting for one person on that turn. Where you talk to it,303A handoff needs a Bot acting for one person on that turn. Where you talk to it,

304and whether it's a personal Bot or a [shared Bot](/grok-bot/shared-bots),304and whether it's a personal Bot or a [shared Bot](/grok-bot/team-bots),

305decide this:305decide this:

306 306 

307| Bot | Where you ask | Can it message other Bots? | Acting for | Where the reply lands |307| Bot | Where you ask | Can it message other Bots? | Acting for | Where the reply lands |


313To hand work between Bots from a Slack channel, share a Bot and add it to Slack.313To hand work between Bots from a Slack channel, share a Bot and add it to Slack.

314A shared Bot has its own Slack app and handle, and anyone in the channel can314A shared Bot has its own Slack app and handle, and anyone in the channel can

315give it work. See [How do I add a shared Bot to315give it work. See [How do I add a shared Bot to

316Slack?](/grok-bot/shared-bots#how-do-i-add-a-shared-bot-to-slack)316Slack?](/grok-bot/team-bots#how-do-i-add-a-team-bot-to-slack)

317 317 

318## Use threads and reactions318## Use threads and reactions

319 319 

Details

121requires can't be removed.121requires can't be removed.

122 122 

123* **Apps are account-wide.** A connected app is available to every Bot you run.123* **Apps are account-wide.** A connected app is available to every Bot you run.

124 A teammate's [shared Bot](/grok-bot/shared-bots) asks before it uses your124 A teammate's [shared Bot](/grok-bot/team-bots) asks before it uses your

125 accounts.125 accounts.

126* **App logins stay off the computer.** OAuth tokens are held on Cursor's126* **App logins stay off the computer.** OAuth tokens are held on Cursor's

127 connector backend, and the Bot invokes tools without receiving them.127 connector backend, and the Bot invokes tools without receiving them.


320 one is deleted.320 one is deleted.

321* **Yours, not one Bot's.** All your Bots can use the address in your own chats321* **Yours, not one Bot's.** All your Bots can use the address in your own chats

322 and routines. It isn't used in Slack threads or in chats where someone else is322 and routines. It isn't used in Slack threads or in chats where someone else is

323 talking to the Bot, and a [shared Bot](/grok-bot/shared-bots) doesn't have a323 talking to the Bot, and a [shared Bot](/grok-bot/team-bots) doesn't have a

324 team address.324 team address.

325* **Reading mail.** Anyone can send mail to the address. Mail that fails the325* **Reading mail.** Anyone can send mail to the address. Mail that fails the

326 spam or virus scan is kept without its body or attachments, and it never326 spam or virus scan is kept without its body or attachments, and it never

faq.md +2 −2

Details

22devices. You can also chat with your Bots in22devices. You can also chat with your Bots in

23[X Chat](/grok-bot/chat-and-collaboration#chat-in-x-chat),23[X Chat](/grok-bot/chat-and-collaboration#chat-in-x-chat),

24[tag @bot on X](/grok-bot/tag-on-x) to hand a post to your Bot, and talk to a24[tag @bot on X](/grok-bot/tag-on-x) to hand a post to your Bot, and talk to a

25[shared Bot in Slack](/grok-bot/shared-bots#how-do-i-add-a-shared-bot-to-slack).25[Team Bot in Slack](/grok-bot/team-bots#how-do-i-add-a-team-bot-to-slack).

26 26 

27## Does Grok Bot keep working when my laptop is closed?27## Does Grok Bot keep working when my laptop is closed?

28 28 


347[Share a Bot](/grok-bot/bots#share-a-bot).347[Share a Bot](/grok-bot/bots#share-a-bot).

348 348 

349To give the team one Bot they all talk to, rather than a copy each person349To give the team one Bot they all talk to, rather than a copy each person

350customizes, publish a [shared Bot](/grok-bot/shared-bots).350customizes, publish a [shared Bot](/grok-bot/team-bots).

351 351 

352## What happens if I delete a Bot?352## What happens if I delete a Bot?

353 353 

Details

269 **Media**, **Links**, **Files**, **Apps**, or **Pinned**, to show only that269 **Media**, **Links**, **Files**, **Apps**, or **Pinned**, to show only that

270 kind. Choose **All** to see everything again.270 kind. Choose **All** to see everything again.

271 271 

272On a [shared Bot](/grok-bot/shared-bots), the desktop Library lists what the272On a [shared Bot](/grok-bot/team-bots), the desktop Library lists what the

273Bot made for you under **Private to you**, and pages shared with your team and273Bot made for you under **Private to you**, and pages shared with your team and

274the Bot's own files under **Bot's files**. There's no **Pinned** heading: hover274the Bot's own files under **Bot's files**. There's no **Pinned** heading: hover

275over a row in **Private to you** and click its pin to keep it at the top. The275over a row in **Private to you** and click its pin to keep it at the top. The

get-started.md +1 −1

Details

85`Cmd/Ctrl+N`. Name the Bot and choose **Create**. On a Cursor team, **+** opens85`Cmd/Ctrl+N`. Name the Bot and choose **Create**. On a Cursor team, **+** opens

86a menu. Choose **Create a Bot** to make one, or **Browse shared Bots** to use a86a menu. Choose **Create a Bot** to make one, or **Browse shared Bots** to use a

87Bot a teammate shared. To share your own Bot with teammates, see87Bot a teammate shared. To share your own Bot with teammates, see

88[Shared Bots](/grok-bot/shared-bots).88[Shared Bots](/grok-bot/team-bots).

89 89 

90To rename a Bot later, click its name at the top of the chat to open its90To rename a Bot later, click its name at the top of the chat to open its

91details, then click the name again to edit it.91details, then click the name again to edit it.

initiative.md +47 −0 created

Details

1#### Use Grok Bot

2 

3# When Your Bot Takes Initiative

4 

5Your Bot doesn't only wait for instructions. It notices work it can take off

6your plate and offers to handle it, and it tells you when something needs your

7attention. You stay in charge: it offers first and asks before risky actions.

8 

9## What does my Bot do without being asked?

10 

11* **Offers to take on work.** Your primary Bot spots tasks it can handle for

12 you and offers to do them.

13* **Flags problems with your apps.** When an app such as Gmail signs you out,

14 your primary Bot tells you in its chat and offers to reconnect.

15* **Follows up.** In [X Chat](/grok-bot/chat-and-collaboration#chat-in-x-chat),

16 a Bot can follow up on a conversation in its own words.

17 

18## Which Bot reaches out to me?

19 

20Your [primary Bot](/grok-bot/bots#your-primary-bot), marked with a star in the

21sidebar. A Team Bot can't be your primary Bot.

22 

23A Team Bot can still ask you for something it needs. For example, when one of

24its routines needs one of your connected apps, it asks in its Slack thread and

25tags you.

26 

27## Does my Bot act on its own or ask first?

28 

29It offers first. When you say yes, it does the work the same way it does any

30task you give it, and it asks before risky actions. See [Approvals, security,

31and privacy](/grok-bot/approvals-security-and-privacy).

32 

33## How do I get fewer alerts from my Bot?

34 

35Turn off **Notifications** for that Bot. On the phone, the switch is in the

36Bot's profile. On desktop, ask the Bot to turn its notifications off. See

37[Control notifications](/grok-bot/settings-and-notifications#control-notifications).

38 

39Notifications control alerts, not the check-ins themselves. If you'd like your

40Bot's check-ins turned off, [contact support](/grok-bot/troubleshooting#before-contacting-support).

41 

42## Related pages

43 

44* [Skills and routines](/grok-bot/skills-routines-and-automations)

45* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

46* [Create and manage Bots](/grok-bot/bots)

47* [Settings and notifications](/grok-bot/settings-and-notifications)

meetings.md +79 −0 created

Details

1#### Use Grok Bot

2 

3# Add a Bot to Your Meetings

4 

5A Bot can join your Google Meet, Zoom, or Microsoft Teams calls. It listens,

6takes notes, answers questions in the meeting chat, and sends you a summary and

7action items when the call ends.

8 

9Meetings are available on Team, Enterprise, and Ultra plans. Enterprise admins

10can turn on Meetings in settings. See [Can a Team Bot join meetings?](#can-a-team-bot-join-meetings)

11 

12## How do I add a Bot to a meeting?

13 

141. Paste the Google Meet, Zoom, or Microsoft Teams link into your chat with the

15 Bot, and ask it to join and take notes.

162. Approve the card when the Bot asks.

173. When the meeting starts, the host admits the Bot. It joins as **Bot name

18 (your first name's Bot) - transcribing**, or **Bot name (Team Bot) -

19 transcribing** for a Team Bot.

20 

21A Bot that follows your calendar can also join scheduled meetings on its own.

22 

23Not sure what to ask? Open the Bot's details. If it hasn't joined a meeting

24before, **Add to meeting** under **Suggested** drafts a question asking the Bot

25how to add it to meetings.

26 

27## How do I manage a Bot's upcoming meetings?

28 

29Open the Bot's details. Meetings it's joining or attending appear under

30**Upcoming**, with a countdown to the join time, the next join time for a

31scheduled meeting, or **Taking notes** while it's in the call.

32 

33Hover a meeting you scheduled and open its menu to see **Meeting actions**:

34 

35* **Disable Interactivity** keeps the Bot listening and taking notes, without

36 answering in the meeting. The row shows **Muted**. While the meeting is still

37 scheduled, **Enable Interactivity** turns it back on. Once the Bot is joining

38 or in the call, quit and add it again to turn it back on.

39* **Cancel** removes a scheduled meeting.

40* **Quit** takes the Bot out of a meeting it's joining or attending.

41 

42## How do I talk to a Bot during a meeting?

43 

44Address the Bot by name in the meeting chat, and it answers there.

45 

46* **Zoom private chat.** A private chat message to the Bot gets a private

47 answer.

48* **Conference rooms.** A request from a conference room device counts as

49 coming from the room, not one person.

50 

51If someone in the meeting asks for something the Bot held back, the Bot tells

52you who asked and offers to send it. It won't share your credentials in a

53meeting.

54 

55## What happens after a meeting?

56 

57When the call ends, the Bot sends a summary and action items in its chat. If you

58have [Pages](/grok-bot/files-and-results#pages), a longer report goes on a page,

59with the link in the chat. Ask the Bot anytime for the summary or transcript of

60a past meeting.

61 

62Meetings use the settings of the person who started them.

63 

64## Can a Team Bot join meetings?

65 

66Yes, when its team allows meetings. On Enterprise plans, admins turn

67meetings on or off for everyone's Bots with **Meetings** under **Bot

68Capabilities** on the Grok Bot page of the team dashboard. When it's off, Bots

69can't join or read meetings, and a Bot that was scheduled to join tells you

70meetings are no longer available. See [Grok Bot for

71teams and enterprises](/grok-bot/teams-and-enterprises#meetings).

72 

73## Related pages

74 

75* [Team Bots](/grok-bot/team-bots)

76* [Use Grok Bot in Microsoft Teams](/grok-bot/microsoft-teams)

77* [Files and results](/grok-bot/files-and-results)

78* [Skills and routines](/grok-bot/skills-routines-and-automations)

79* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

microsoft-teams.md +116 −0 created

Details

1#### Use Grok Bot

2 

3# Use Grok Bot in Microsoft Teams

4 

5Bring a [Team Bot](/grok-bot/team-bots) into Microsoft Teams so your team can

6mention it in channels, chat with it directly, and add it to group chats. It

7works the way it does in Slack: it acts for the person who asked, uses their

8usage, and asks before risky actions.

9 

10## What do I need before adding a Bot to Microsoft Teams?

11 

12* A published Team Bot. You must be its owner or a Manager.

13* Microsoft Teams turned on for your Cursor team by a team admin. See [How does

14 a team admin turn on Microsoft

15 Teams?](#how-does-a-team-admin-turn-on-microsoft-teams)

16* A Microsoft account in the organization that uses Teams.

17 

18## How does a team admin turn on Microsoft Teams?

19 

201. On the Grok Bot page of the team dashboard, under **Shared Bots**, choose

21 **Enable** next to **Enable Microsoft Teams**.

222. Sign in with a Microsoft Teams or Global administrator account and accept

23 the permissions Microsoft shows.

24 

25The row then shows that Microsoft Teams is enabled for your organization. Bot

26owners on the team can now connect their own Bots. **Revoke** turns it off. A

27Microsoft Teams admin still approves each Bot in the Teams admin center.

28 

29## How do I add a Team Bot to Microsoft Teams?

30 

31The owner or a Manager connects it, after publishing:

32 

331. Open the Bot's details and find **Bring to your team's Microsoft Teams**, or

34 choose **Manage** and look under **Channels**. Choose **Connect Microsoft

35 Teams**.

362. Finish signing in with Microsoft in the browser window that opens. Confirm

37 it's the right account, and choose an organization if you belong to more

38 than one.

393. While the dialog says **Waiting on admin approval**, a Microsoft Teams admin

40 needs to approve the Bot in the Teams admin center, under **Teams apps** >

41 **Manage apps** > **Pending approval**. Microsoft doesn't notify them, so

42 send them the link the dialog shows. Choose **Check again** right after they

43 approve, or **Cancel request** to stop.

44 

45Once it's approved, Microsoft Teams finishes setting up the Bot on its own,

46which can take up to an hour. The dialog then says the Bot is in Microsoft

47Teams, with **Open in Teams**. To use it in a channel, add it to a team from

48Microsoft Teams, and the dialog lists the teams it's been added to.

49 

50If a Teams admin declines the Bot, the dialog shows their note. Make any changes

51and choose **Resubmit**.

52 

53## How do I link my Microsoft Teams account?

54 

55The Bot needs to know who you are before it can act for you. The first time you

56message it, it replies with a **Link Account** card that only you can see.

57Choose it and sign in with your Microsoft account.

58 

59You can also link first: open **Settings** > **General** > **Team Bots** and

60choose **Link** next to **Microsoft Teams account**. If it says your admin

61hasn't turned on Microsoft Teams for your organization yet, ask a Cursor team

62admin to enable it.

63 

64## What can a Bot do in Microsoft Teams?

65 

66* **Answer in channels and chats.** Mention the Bot in a channel of a team it

67 joined, add it to a group chat, or message it directly.

68* **Read the conversation.** It reads the thread it's in, and the channels of

69 the teams it joined.

70* **Work with files.** It reads files attached to posts and sends you files

71 through your OneDrive. If you ask for a file in a channel or group chat, it

72 asks you to message it directly instead.

73* **Act for you.** It uses your usage and asks you before risky actions, the

74 same as in Slack. See [How do approvals work on a Team

75 Bot?](/grok-bot/team-bots#how-do-approvals-work-on-a-team-bot)

76 

77To have a Bot join a Teams call and transcribe it, see [Add a Bot to your

78meetings](/grok-bot/meetings).

79 

80## How do I update or remove a Bot in Microsoft Teams?

81 

82* **Name or picture.** After you change them, the dialog says the Bot's name or

83 avatar changed. Choose **Update in Teams**. If your Teams admin has to approve

84 the change, it shows **An update is waiting for your Teams admin**.

85* **Remove it.** Choose **Remove from Microsoft Teams** in the same dialog. This

86 removes the app from your Microsoft Teams organization, and teammates can't

87 reach the Bot there until it's added again.

88* **Disconnect your Microsoft account.** This disconnects it from every Bot you

89 own in that organization, not only this one. Bots already in Teams keep

90 answering there.

91* **Delete the Bot.** Deleting a Bot also removes it from Microsoft Teams.

92 

93## Why isn't my Bot in Microsoft Teams?

94 

95| What you see | What it means |

96| --- | --- |

97| **Microsoft Teams isn't enabled** for your team | A team admin needs to choose **Enable Microsoft Teams** on the Grok Bot page of the team dashboard. |

98| **Publish this Bot to your team first, then add it to Microsoft Teams** | The Bot is still a draft. Choose **Publish**, then connect. |

99| **Waiting on admin approval** | Your Teams admin hasn't approved the Bot. Send them the link in the dialog, then choose **Check again**. |

100| **Your Teams admin declined** the Bot | Check their note, make changes, and choose **Resubmit**. |

101| **Microsoft Teams didn't accept the app** | Your organization doesn't allow custom apps in Teams. A Teams admin can allow them. Choose **Download app package** and send it to your Teams admin to upload. |

102| **Blocked by your organization's Teams app policy** | A Microsoft Teams admin needs to allow the app in the Teams admin center. |

103| **Need admin approval** | The Microsoft sign-in needs an admin's consent. Send a Microsoft Teams or Global admin the link the dialog shows, then connect again. |

104| **Microsoft Teams stopped working for your team** | The team's connection expired. A Cursor team admin needs to choose **Reconnect Microsoft Teams** on the dashboard. |

105| **Finishing setup in Microsoft Teams** | The Bot is approved and Teams is still setting it up. This can take up to an hour and finishes on its own. |

106| A **Link Account** card | Your Microsoft account isn't linked yet. Choose it and sign in. |

107 

108If none of these match, [contact support](/grok-bot/troubleshooting) with the

109Bot's name, the exact message, and your Grok Bot version.

110 

111## Related pages

112 

113* [Team Bots](/grok-bot/team-bots)

114* [Add a Bot to your meetings](/grok-bot/meetings)

115* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

116* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises#microsoft-teams)

security.md +53 −2

Details

39| Mode | Effect |39| Mode | Effect |

40| --- | --- |40| --- | --- |

41| **Allow All Network Access** | All destinations. Teams without a policy get this. |41| **Allow All Network Access** | All destinations. Teams without a policy get this. |

42| **Allow All Sites Except These** | All destinations except the sites you block. See [Blocked sites](#blocked-sites). |

42| **Defaults + Team Allowlist** | Cursor's default destinations plus your list |43| **Defaults + Team Allowlist** | Cursor's default destinations plus your list |

43| **Team Allowlist Only** | Only your list, plus the destinations a computer needs to function |44| **Team Allowlist Only** | Only your list, plus the destinations a computer needs to function |

44 45 

45* **Destinations** cover web domains as well as IP ranges with ports for raw46* **Destinations** in the allowlist modes cover web domains as well as IP

46 connections, with no cap on the number of entries.47 ranges with ports for raw connections, with no cap on the number of entries.

47* **Directory groups. Enterprise only, inside Network Controls.** Groups can48* **Directory groups. Enterprise only, inside Network Controls.** Groups can

48 set their own network policy, which replaces the team's for their members,49 set their own network policy, which replaces the team's for their members,

49 and a lock makes the team policy effective for everyone.50 and a lock makes the team policy effective for everyone.


59and the network policy are separate layers, and closing both paths takes both60and the network policy are separate layers, and closing both paths takes both

60controls.61controls.

61 62 

63### Blocked sites

64 

65**Allow All Sites Except These** lets team computers reach every destination

66except the sites you list under **Blocked Sites**. A group picks

67**Team Policy, Except These Sites** to block more sites on top of the team

68policy. A team or group uses either an allowlist or blocked sites, not both.

69 

70* **Hostnames only.** Enter one site per line, such as `example.com`, with no

71 scheme, port, or path. IP addresses are not accepted. Each site also blocks

72 its subdomains, so `example.com` and `*.example.com` are the same entry, and

73 the list saves them as one.

74* **Up to 50 sites.** The limit counts the team's list and every group's list

75 together.

76* **Sites Grok Bot needs stay open.** A save is refused when the list names a

77 site the computer needs to run, or one Grok Bot reaches through Cursor's

78 proxy.

79* **What it covers.** Shell commands and the browser on the computer,

80 WebFetch, and connected apps (MCP servers). A remote MCP server on a blocked

81 site is refused without **Apply to MCP servers**. When a member routes

82 traffic through their desktop, blocked sites stay blocked on that route too.

83* **When it applies.** A change reaches computers without a reset.

84 * Running computers usually pick up a change within about a minute.

85 Sleeping computers pick it up when they next wake.

86 * Web fetches in a task that is already running finish with the previous

87 list. The new list applies from the next task.

88 * For MCP servers, a change can take up to about a minute to apply.

89 * A computer that

90 [routes traffic through the member's desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop)

91 may restart once at an idle moment to apply a change, keeping files and

92 sign-ins. If you change the list several times in a day, a later change

93 may wait for the next restart. To apply it right away, recreate the

94 computer from

95 [Manage Member Computers and Data](/grok-bot/teams-and-enterprises#manage-member-computers-and-data).

96 

97Know the limits before you rely on it:

98 

99* **Best effort, not a security boundary.** Matching is by hostname. A request

100 to a bare IP address gets through, and so can some apps and encrypted

101 connections.

102* **WebSearch is not filtered.** Search results can still list pages from a

103 blocked site. Opening one with WebFetch or the browser is refused.

104* **WebFetch stops rendering pages.** While a list blocks any site, WebFetch

105 reads pages as plain HTML without running their scripts, for everyone the

106 list applies to. Pages that build their content with JavaScript can come

107 back empty.

108* **No block page in the browser.** A blocked HTTPS site shows a browser

109 security or connection error, not a page that says the site is blocked.

110 Shell commands get an HTTP 403 response, and WebFetch and MCP return a

111 message naming the blocked site.

112 

62### MCP servers and the network policy113### MCP servers and the network policy

63 114 

64The network policy governs where team computers send traffic. Connected apps115The network policy governs where team computers send traffic. Connected apps

security-faq.md +9 −1

Details

16user, every Bot shares that computer. Treat a login or file on the computer as16user, every Bot shares that computer. Treat a login or file on the computer as

17available to every Bot that user runs. When a workload needs its own computer17available to every Bot that user runs. When a workload needs its own computer

18and credential set, give it its own Cursor user. A teammate's18and credential set, give it its own Cursor user. A teammate's

19[shared Bot](/grok-bot/shared-bots) usually works on a user's computer during19[shared Bot](/grok-bot/team-bots) usually works on a user's computer during

20that user's own chat with it.20that user's own chat with it.

21 21 

22### What can a Bot access?22### What can a Bot access?


50see it and cannot set a destination allowlist. Teams without a policy default50see it and cannot set a destination allowlist. Teams without a policy default

51to allow-all. See [network policy](/grok-bot/security#network-policy).51to allow-all. See [network policy](/grok-bot/security#network-policy).

52 52 

53### Can we block a few sites instead of using an allowlist?

54 

55Yes. Pick **Allow All Sites Except These** in **Network Controls** and list up

56to 50 hostnames; each one also blocks its subdomains. It covers the computer's

57shell and browser, WebFetch, and MCP servers. It is best effort, not a

58security boundary: a bare IP address gets through, and WebSearch results are

59not filtered. See [Blocked sites](/grok-bot/security#blocked-sites).

60 

53### Do admin controls apply per group, or only org-wide?61### Do admin controls apply per group, or only org-wide?

54 62 

55Directory-group scope is part of **Network Controls**, which is Enterprise63Directory-group scope is part of **Network Controls**, which is Enterprise

shared-bots.md +0 −317 deleted

File Deleted View Diff

1#### Use Grok Bot

2 

3# Shared Bots

4 

5A Bot is either personal or shared. Share a Bot with your Cursor team the way

6you'd share a doc: with everyone on the team, or only with certain people and

7groups. Sharing doesn't make a copy, and each person's chat with a shared Bot is

8private.

9 

10Shared Bots always run in the cloud. A Bot that runs on your own computer can't

11be shared.

12 

13## Who can use shared Bots?

14 

15Shared Bots are for members of a Cursor team who have Grok Bot. Choose **+** in

16the sidebar to see **Create a Bot** and **Browse shared Bots**. If **Browse

17shared Bots** isn't there, you aren't on a Cursor team, or your Grok Bot app

18needs an update.

19 

20## How do I create a Bot for my team?

21 

221. Choose **+** in the sidebar, then **Create a Bot**, and give it a name.

232. Tell the Bot what it should help the team with. A sentence is enough.

243. Follow its setup steps for apps, secrets, skills, and files. Only add keys

25 and files you're happy for everyone you share it with to use.

264. Share it. See [How do I share a Bot with my

27 team?](#how-do-i-share-a-bot-with-my-team)

28 

29You can also share a Bot you already have. Sharing doesn't duplicate it. Before

30you share, check its apps, secrets, skills, and files, since they work in every

31teammate's chat.

32 

33## How do I share a Bot with my team?

34 

35Choose **Share** at the top right of the Bot's chat. In **Share this Bot**:

36 

37* Under **Who has access**, choose your team to share the Bot with everyone on

38 the team. If your team is part of an organization, choose the organization

39 to share it with everyone in it. Choose **People you invite** to share it only with the people

40 and groups you add. Limiting it asks you to confirm with **Limit access**.

41 The owner and Managers can always use the Bot.

42* Search under **Add people or groups** to add someone. People you add can chat

43 with the Bot as a **Collaborator**. In the list of people who have access,

44 open a person's role and choose **Manager** to let them also change how the

45 Bot works and share it with others.

46 

47To stop sharing, the owner can choose **Only you** under **Who has access**.

48This removes everyone else after you confirm with **Remove**. To remove one

49person or group, open their role in the list and choose **Remove**.

50 

51## How do teammates find a shared Bot?

52 

53* Choose **+** in the sidebar, then **Browse shared Bots**. The list shows Bots

54 shared with you, and each one shows who made it. Choose **Add** to keep a Bot

55 in your sidebar.

56* In the desktop app, press `Cmd/Ctrl+K` and choose **Browse shared Bots** at

57 the bottom of the list. You can also type a shared Bot's name and choose it

58 to add it.

59* Ask one of your Bots in your own chat, for example "Is there a shared Bot

60 for on-call triage?" It searches the shared Bots you can use by what they do,

61 and tells you which ones you've already added.

62* On your phone, tap **+**, then **Browse shared Bots**.

63* Open a link a teammate sent you, then choose **Start a chat**.

64 

65A shared Bot's link opens the same Bot for everyone. It's different from

66[sharing a Bot template](/grok-bot/bots#share-a-bot), which gives each person

67their own copy.

68 

69## Can the owner see my chats with a shared Bot?

70 

71No. Each person's chat with a shared Bot is private. The owner and Managers

72can't read your chats, and you can't read the owner's or anyone else's.

73 

74The Bot can save things it learns for the whole team, and it tells you when it

75does. It doesn't save anything about you personally for the team. What it

76remembers about working with you stays between you and the Bot.

77 

78## Whose apps and secrets does a shared Bot use?

79 

80A shared Bot uses the apps and secrets its owner added. Those work the same for

81everyone who chats with it.

82 

83In your own chat with a shared Bot, it can also use your apps. It asks before it

84uses one of your personal accounts. The card says **Allow**, then the app name:

85 

86* **Allow once** lets it use that account this time.

87* **Always allow** remembers your answer. Its menu has **Always allow for your

88 messages to this Bot** and **Always allow for your messages to every Shared

89 Bot**.

90* **Skip** means it doesn't use that account this time.

91 

92In Slack channels, threads, and group chats, a shared Bot uses only its owner's

93apps, and asks before it uses your accounts.

94 

95To make every shared Bot ask again, open **Settings** > **General** > **Shared

96Bots** and choose **Clear** next to **Clear connector preferences**.

97 

98## Which computer does a shared Bot use?

99 

100In your own chat with a teammate's shared Bot, the Bot usually works on your

101Grok Bot computer. That means it can use the files there and the sites you're

102signed in to there. Sometimes it uses a separate computer just for that

103conversation, for example when your privacy mode is stricter than the owner's.

104 

105When you DM a shared Bot in Slack, it also works on your own computer. In Slack

106channels, threads, group DMs, and group chats, a shared Bot uses one shared

107computer of its own.

108 

109## Whose usage pays for a shared Bot chat?

110 

111A shared Bot reply uses the Grok Bot usage of the person it's answering. That's

112true in your own chat, in Slack, and in group chats. Your own limits apply. The

113owner's usage pays for the owner's own messages, and for Slack posts from apps

114or workflows that aren't linked to a Cursor account. See [How much does Grok Bot

115cost?](/grok-bot/faq#how-much-does-grok-bot-cost)

116 

117## How do approvals work on a shared Bot?

118 

119A shared Bot asks the person it's answering before risky actions.

120 

121* In your own chat with a shared Bot, you answer its approval cards.

122* In a Slack thread, the Bot posts a **Review an action** card with **Allow

123 once**, **Deny**, and **View details**. Only the person who asked can answer

124 it.

125* In a group chat, only the person whose message the Bot is answering can

126 answer.

127 

128It also asks before it uses your personal accounts. See [Whose apps and secrets

129does a shared Bot use?](#whose-apps-and-secrets-does-a-shared-bot-use) For the

130rest of the approval model, see [Approvals, security, and

131privacy](/grok-bot/approvals-security-and-privacy).

132 

133## How do I add a shared Bot to Slack?

134 

135The owner or a Manager adds it, after sharing:

136 

1371. Open the Bot's details, or choose **Manage** and look under **Channels**.

1382. Find **Bring to your team's Slack** or **Slack**, and choose **Connect**.

1393. If it says **Awaiting admin approval**, a Slack workspace admin needs to

140 approve the app.

141 

142Once it says **Connected**, teammates can message the Bot directly or mention it

143in channels.

144 

145In a channel thread or a DM, the shared Bot acts for the teammate who mentioned

146it. It can hand work to that person's own Bots, and their replies are posted

147back into the same thread. A personal Bot doesn't hand work to other Bots from a

148channel thread. See [Let Bots hand work

149off](/grok-bot/chat-and-collaboration#let-bots-hand-work-off).

150 

151Bots record who asked for each message they post in Slack, so anyone in the

152thread can ask the Bot who requested it. When a shared Bot's routine replies in a

153Slack thread, the Bot follows that thread and answers later replies without an

154@mention.

155 

156Each teammate needs to link their Slack account first. Open **Settings** >

157**General** > **Shared Bots** and choose **Link**. If you message the Bot before

158you link, it replies with steps to link your account.

159 

160## How do I add a shared Bot to Microsoft Teams?

161 

162A team admin first enables Microsoft Teams for the team on the Grok Bot page of

163the dashboard. See [Microsoft

164Teams](/grok-bot/teams-and-enterprises#microsoft-teams). Then the owner or a

165Manager adds the Bot, after sharing:

166 

1671. Open the Bot's details and find **Bring to your team’s Microsoft Teams**, or

168 choose **Manage** and look under **Channels**. Choose **Connect**.

1692. Finish signing in with Microsoft in the browser window that opens, then

170 choose the teams the Bot should join.

1713. While it says **Waiting on admin approval**, a Microsoft Teams admin needs to

172 approve the Bot in the Teams admin center, under **Teams apps** > **Manage

173 apps** > **Pending approval**. Microsoft doesn't notify them, so send them

174 the link the dialog shows. Setup finishes by itself once they approve.

175 Choose **Check again** to check right after they approve, or

176 **Cancel request** to stop.

177 

178If the dialog says **Microsoft Teams didn't accept the app**, your organization

179may not allow custom apps in Microsoft Teams. A Teams admin can allow them, and

180the dialog offers **Download app package** for the admin.

181 

182If **Channels** shows **Not connected · Blocked by your organization's Teams app

183policy**, a Microsoft Teams admin needs to allow the app in the Teams admin

184center.

185 

186Once it's connected, teammates can chat with the Bot or mention it in a channel

187of a team it joined, and it replies in the same conversation.

188 

189If you change the Bot's name or avatar, choose **Update in Teams**. Updates also

190wait for a Teams admin, and show **An update is waiting for your Teams admin**

191until they approve. If the admin declines the Bot, choose **Resubmit**.

192 

193Each teammate links their Microsoft Teams account under **Settings** >

194**General** > **Shared Bots**: choose **Link** next to **Microsoft Teams

195account**.

196 

197## How do I edit or delete a shared Bot?

198 

199The owner and the Bot's Managers can change a shared Bot. Its details show in

200the panel on the right of the chat:

201 

202* **Plugins** (the Bot's connected apps), **Secrets**, **Skills**, and

203 **Files** hold what the Bot uses for everyone.

204* Click the name to rename the Bot. Edit the description under **About**.

205* **Share** controls who can use the Bot and who manages it.

206 

207Choose the wrench, **Manage**, for the rest:

208 

209* **General** has the Bot's settings, such as whether Collaborators can set up

210 routines, its channels such as Slack and Microsoft Teams, and the **Bot's

211 accounts** it signs in to apps with.

212* **Knowledge** shows what the Bot learned for everyone, and its skills. New

213 learnings wait under **To review** until you choose **Approve** or

214 **Reject**.

215* **Analytics**, when shown, has the Bot's messages, hours saved, and top users.

216 

217The owner can also rename the Bot by right-clicking it in the sidebar and

218choosing **Rename Bot**.

219 

220Only the owner can delete a shared Bot. Right-click the Bot in the sidebar and

221choose **Delete**. This deletes the Bot for your whole team. Teammates lose it,

222along with their chats and routines on it. It can't be undone.

223 

224## How do I remove a shared Bot from my sidebar?

225 

226Right-click the Bot and choose **Remove from sidebar**. To add it back, choose

227**+** in the sidebar, then **Browse shared Bots**, and choose **Add** next to

228it.

229 

230If your admin added the Bot to your sidebar for you, **Remove from sidebar**

231isn't in its menu, and you can't remove it.

232 

233## Can I use shared Bots on my phone?

234 

235Yes. Shared Bots you've added appear in the [phone app](/grok-bot/mobile). To

236find another, tap **+**, then **Browse shared Bots**. Each Bot in the list

237shows how many people use it, and **Add** keeps it in your list. You can chat

238with shared Bots and answer their **Allow** cards. A shared Bot can't be your

239[primary Bot](/grok-bot/bots#your-primary-bot).

240 

241To remove a teammate's Bot from your list, touch and hold it and choose

242**Remove from sidebar**.

243 

244The owner and Managers can also manage a shared Bot from its profile on the

245phone:

246 

247* **Share** opens **Share this Bot**, where you choose who has access and add

248 people. If you're on more than one team, choose a team before you share.

249* **Tools** has the Bot's service accounts, and **Slack** adds the Bot to Slack

250 with your own Slack connection. See [How do I add a shared Bot to

251 Slack?](#how-do-i-add-a-shared-bot-to-slack)

252* **Skills** lists the Bot's skills. Tap **+** to choose **Add Custom Skill**

253 or **Import Existing Skill**, and open a skill to edit it and choose **Save

254 changes**.

255* **Learnings** shows how many learnings are waiting, for example "3 to

256 review". Choose **Approve** or **Reject** on each one.

257* **Routines** lists the Bot's routines, with **Add routine** and the

258 **Collaborators can create routines** switch.

259* **Analytics**, when shown, has weekly and daily active users, messages, hours

260 saved, and top users, over **7 days**, **30 days**, or **90 days**.

261 

262When you ask one of your own Bots on the phone to work with your team, it shows

263a **Team access** card. **Share** moves that Bot to the team with its chat and

264memories, or **Copy** makes a team copy and keeps the original private. **Start

265fresh** creates a new shared Bot without this chat or its memories.

266 

267## Can I voice chat with a teammate's shared Bot?

268 

269Yes, on desktop. In your own chat with the Bot, choose **Start voice chat**. See

270[Start a voice chat](/grok-bot/chat-and-collaboration#start-a-voice-chat).

271 

272## Can a shared Bot join a group chat?

273 

274Yes. You can add a Bot a teammate shared with you to your own group chat. It

275can't share a group with Bots that run on your own computer. See [Start a group

276chat](/grok-bot/chat-and-collaboration#start-a-group-chat).

277 

278## How do admins manage shared Bots?

279 

280On the Grok Bot page of the [Cursor dashboard](https://cursor.com/dashboard/bot),

281open **Manage Bots** under **Shared Bots**.

282 

283* **Access** shows who can use each shared Bot. Click it to change who can use

284 the Bot.

285* **Auto-add** puts the Bot in members' sidebars automatically. Pick **All

286 team** or one or more groups. Those members can't hide it. Auto-add only

287 applies to groups that have access.

288 

289See [Grok Bot for teams and

290enterprises](/grok-bot/teams-and-enterprises#manage-bots).

291 

292## Why can't I see or use a shared Bot?

293 

294| What you see | What it means |

295| --- | --- |

296| **Browse shared Bots** isn't under **+** | You aren't on a Cursor team, or your Grok Bot app needs an update. |

297| **Shared Bots Not Available** | Your account doesn't have access to shared Bots. |

298| **Bot Not Found** | The Bot may have been removed, or it isn't shared with you. |

299| **No Access to This Bot** | The Bot is shared only with certain people. Ask its owner or a Manager for access. |

300| A teammate's Bot isn't in **Browse shared Bots** | The owner hasn't shared it with you yet. |

301| **Your usage limit has been reached** | Your Grok Bot usage ran out. Your chats with a teammate's shared Bot use your usage. See [How much does Grok Bot cost?](/grok-bot/faq#how-much-does-grok-bot-cost) |

302| **This Bot's owner has reached their usage limit** | This reply was billed to the owner's account, and the owner's usage ran out. Ask the owner to check their plan. |

303| **This conversation can't run on your computer because your privacy mode is stricter than the bot owner's.** | Your privacy mode setting is stricter than the owner's, so this chat can't use your computer. |

304| In Slack, the Bot asks you to link a Cursor account | Link your Slack account under **Settings** > **General** > **Shared Bots**, using the Cursor account on the Bot's team. |

305 

306If none of these match, [contact support](/grok-bot/troubleshooting) with the

307Bot's name, the exact message, and your Grok Bot version.

308 

309## Related pages

310 

311* [Create and manage Bots](/grok-bot/bots)

312* [Message and collaborate](/grok-bot/chat-and-collaboration)

313* [Use the computer and apps](/grok-bot/computer-and-apps)

314* [Vault and secure sign-in](/grok-bot/vault)

315* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

316* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

317* [Troubleshooting](/grok-bot/troubleshooting)

team-bots.md +398 −0 created

Details

1#### Use Grok Bot

2 

3# Team Bots

4 

5A Bot is either personal or a Team Bot. Share a Bot the way you'd share a doc:

6with your Cursor team, your whole organization, or only certain people and

7groups. Sharing doesn't make a copy, and each person's chat with a Team Bot is

8private.

9 

10Team Bots always run in the cloud. A Bot that runs on your own computer can't

11be shared. A few screens, such as **Browse shared Bots**, still say Team Bots.

12They're the same thing.

13 

14## Who can use Team Bots?

15 

16Team Bots are available on Team and Enterprise plans, for members who have Grok

17Bot. Choose **+** in

18the sidebar to see **Create a Bot** and **Browse shared Bots**. If **Browse

19Team Bots** isn't there, you aren't on a Cursor team, or your Grok Bot app

20needs an update.

21 

22In Slack, members of your workspace who aren't on the team can sometimes use a

23Team Bot too. See [Who can talk to a Team Bot in

24Slack?](#who-can-talk-to-a-team-bot-in-slack)

25 

26## How do I create a Bot for my team?

27 

281. Choose **+** in the sidebar, then **Create a Bot**, and give it a name.

292. Tell the Bot what it should help the team with. A sentence is enough.

303. Follow its setup steps for apps, secrets, skills, and files. Only add keys

31 and files you're happy for everyone you share it with to use. Until you

32 publish it, it's a draft only you can see.

334. When the Bot says it's ready to share, choose **Publish**. Teammates can

34 then find it. To change who has access, see [How do I share a Bot with my

35 team?](#how-do-i-share-a-bot-with-my-team)

36 

37You can also share a Bot you already have. Sharing doesn't duplicate it. Before

38you share, check its apps, secrets, skills, and files, since they work in every

39teammate's chat.

40 

41## How do I share a Bot with my team?

42 

43Choose **Share** at the top right of the Bot's chat. In **Share this Bot**:

44 

45* Under **Who has access**, choose your team to share the Bot with everyone on

46 the team. If your team is part of an organization, choose the organization

47 to share it with everyone in it. Choose **People you invite** to share it only with the people

48 and groups you add. Limiting it asks you to confirm with **Limit access**.

49 The owner and Managers can always use the Bot.

50 

51* Search under **Add people or groups** to add someone. People you add can chat

52 with the Bot as a **Collaborator**. In the list of people who have access,

53 open a person's role and choose **Manager** to let them also change how the

54 Bot works and share it with others.

55 

56* Choose **Copy link** to send teammates a link to the Bot.

57 

58To stop sharing, the owner can choose **Only you** under **Who has access**.

59This removes everyone else after you confirm with **Remove**. To remove one

60person or group, open their role in the list and choose **Remove**.

61 

62## Who can share Bots?

63 

64Anyone on the team, unless an admin changes it. On the Grok Bot page of the team

65dashboard, **Bot sharing** under **Sharing** is set to **Everyone** or **Admins

66only**. With **Admins only**, **Share** is disabled for members and shows **Only

67team admins can share Bots**. Bots that were already shared stay shared, and

68their owners and Managers can still use them. Ask an admin to share a Bot for

69you, or to change the setting. See [How do admins manage Team

70Bots?](#how-do-admins-manage-team-bots)

71 

72## How do teammates find a Team Bot?

73 

74* Choose **+** in the sidebar, then **Browse shared Bots**. The list shows Bots

75 shared with you, and each one shows who made it. Choose **Add** to keep a Bot

76 in your sidebar.

77* In the desktop app, press `Cmd/Ctrl+K` and choose **Browse shared Bots**.

78 The list starts with **Popular** Bots, and you can search it. You can also

79 type a Team Bot's name and choose it to add it.

80* Ask one of your Bots in your own chat, for example "Is there a Team Bot

81 for on-call triage?" It searches the Team Bots you can use by what they do,

82 and tells you which ones you've already added.

83* On your phone, tap **+**, then **Browse shared Bots**.

84* Open a link a teammate sent you, then choose **Start a chat**.

85 

86A Team Bot's link opens the same Bot for everyone. It's different from

87[sharing a Bot template](/grok-bot/bots#share-a-bot), which gives each person

88their own copy.

89 

90## Can the owner see my chats with a Team Bot?

91 

92No. Each person's chat with a Team Bot is private. The owner and Managers

93can't read your chats, and you can't read the owner's or anyone else's.

94 

95The Bot can learn things for the whole team. What it learns from a teammate

96waits until the owner or a Manager approves it under **Review learnings**. It

97doesn't save anything about you personally for the team. What it remembers

98about working with you stays between you and the Bot. See [What does a Team Bot

99learn for the team?](#what-does-a-team-bot-learn-for-the-team)

100 

101## What does a Team Bot learn for the team?

102 

103A Team Bot keeps team memory and skills that everyone who uses it benefits

104from. When a teammate teaches it something for the team, such as a better way

105to do a task, the Bot suggests the change instead of saving it straight away.

106 

107* Suggested memory and skill changes wait until the owner or a Manager approves

108 them. Owners and Managers see **Review learnings**, with the number waiting,

109 under **Suggested** in the Bot's details. Each one says what it does, such as

110 **Updates the skill** or **Forgets a team memory**, with **Approve** and

111 **Reject**.

112* Changes the owner or a Manager makes in the Bot's main chat apply right away.

113 

114What the Bot learns about you personally stays between you and the Bot. It

115isn't saved for the team.

116 

117## Whose apps and secrets does a Team Bot use?

118 

119A Team Bot uses the apps and secrets its owner added. Those work the same for

120everyone who chats with it.

121 

122In your own chat with a Team Bot, it can also use your apps. It asks before it

123uses one of your personal accounts. The card says **Allow**, then the app name:

124 

125* **Allow once** lets it use that account this time.

126* **Always allow** remembers your answer. Its menu has **Always allow for your

127 messages to this Bot** and **Always allow for your messages to every Team

128 Bot**.

129* **Skip** means it doesn't use that account this time.

130 

131In Slack channels, threads, and group chats, a Team Bot uses only its owner's

132apps, and asks before it uses your accounts.

133 

134A connected account acts as the person the Bot is answering. One teammate's

135connection is never used for someone else, unless a Manager shares it as a

136shared connector.

137 

138To make every Team Bot ask again, open **Settings** > **General** > **Team

139Bots** and choose **Clear** next to **Clear connector preferences**.

140 

141## How do shared connectors work?

142 

143A shared connector lets everyone use an app through one account, so teammates

144don't each have to connect it. The owner or a Manager sets it up: open the

145Bot's details and, under **Setup**, choose **Service accounts**. Pick an app

146under **Shared connectors**, then choose how the Bot signs in to it:

147 

148* **Use individual accounts**: each teammate connects their own.

149* **Share your account**: everyone who uses the Bot acts through your account,

150 including to make changes. Connect the app for yourself first, and only share

151 an account that holds nothing sensitive or private.

152* The Bot's own account: a separate account the Bot uses for the team. Some

153 apps don't support this yet.

154 

155Sharing your account needs a team admin to turn on **Allow Shared Logins**

156first. Until then, the Bot says **Your admin has turned off sharing logins with

157Bots**. See [How do admins manage Team Bots?](#how-do-admins-manage-team-bots)

158 

159The app's row shows whose account the Bot uses. To stop, choose **Stop

160sharing**, or remove the app. Teammates then connect their own.

161 

162## Which computer does a Team Bot use?

163 

164In your own chat with a teammate's Team Bot, the Bot usually works on your

165Grok Bot computer. That means it can use the files there and the sites you're

166signed in to there. Sometimes it uses a separate computer just for that

167conversation, for example when your privacy mode is stricter than the owner's.

168 

169When you DM a Team Bot in Slack, it also works on your own computer. In Slack

170channels, threads, group DMs, and group chats, a Team Bot uses one shared

171computer of its own.

172 

173## Whose usage pays for a Team Bot chat?

174 

175A Team Bot reply uses the Grok Bot usage of the person it's answering. That's

176true in your own chat, in Slack, and in group chats. Your own limits apply. The

177owner's usage pays for the owner's own messages, and for Slack posts from apps

178or workflows that aren't linked to a Cursor account. A reply to someone in

179Slack who hasn't linked an account or isn't on the team uses the team's usage.

180See [How much does Grok Bot

181cost?](/grok-bot/faq#how-much-does-grok-bot-cost)

182 

183## How do approvals work on a Team Bot?

184 

185A Team Bot asks the person it's answering before risky actions.

186 

187* In your own chat with a Team Bot, you answer its approval cards.

188* In a Slack thread, the Bot posts a **Review an action** card with **Allow

189 once**, **Deny**, and **View details**. Only the person who asked can answer

190 it.

191* In a group chat, only the person whose message the Bot is answering can

192 answer.

193 

194It also asks before it uses your personal accounts. See [Whose apps and secrets

195does a Team Bot use?](#whose-apps-and-secrets-does-a-team-bot-use) For the

196rest of the approval model, see [Approvals, security, and

197privacy](/grok-bot/approvals-security-and-privacy).

198 

199## How do I add a Team Bot to Slack?

200 

201The owner or a Manager adds it, after sharing:

202 

2031. Open the Bot's details, or choose **Manage** and look under **Channels**.

2042. Find **Bring to your team's Slack** or **Slack**, and choose **Connect**.

2053. If it says **Awaiting admin approval**, a Slack workspace admin needs to

206 approve the app.

207 

208Once it says **Connected**, teammates can message the Bot directly or mention it

209in channels.

210 

211In a channel thread or a DM, the Team Bot acts for the teammate who mentioned

212it. It can hand work to that person's own Bots, and their replies are posted

213back into the same thread. A personal Bot doesn't hand work to other Bots from a

214channel thread. See [Let Bots hand work

215off](/grok-bot/chat-and-collaboration#let-bots-hand-work-off).

216 

217Bots record who asked for each message they post in Slack, so anyone in the

218thread can ask the Bot who requested it. When a Team Bot's routine replies in a

219Slack thread, the Bot follows that thread and answers later replies without an

220@mention.

221 

222Link your Slack account so the Bot knows who you are and can use your apps.

223Open **Settings** > **General** > **Team Bots** and choose **Link**. If you

224message the Bot before you link, it replies with steps to link your account.

225 

226## Who can talk to a Team Bot in Slack?

227 

228It depends on who the Bot is shared with.

229 

230* **Your organization**: any full member of your Slack workspace can mention it

231 in channels and threads, even without a linked account or a seat on your

232 team. Without a linked account, they're told once per thread that **some

233 features will be limited**. In a DM, they still need to link first. The same

234 goes for a Bot shared with your team when the team isn't in an organization,

235 or is the only team in it.

236* **Your team, or certain people**: only people it's shared with. A linked

237 teammate without access is told the Bot **hasn't been shared with you yet**.

238 Add them under **Share this Bot**. Someone without a linked account is asked

239 to link one.

240* **A personal Bot** only chats with its owner.

241 

242Slack guests, Slack Connect channels, and other Slack workspaces are never

243included. If your Slack email matches an account that already has access, the

244Bot asks you to link it instead.

245 

246A team admin can turn this off for workspace members who aren't on the team.

247See [How do admins manage Team Bots?](#how-do-admins-manage-team-bots)

248 

249## How do I add a Team Bot to Microsoft Teams?

250 

251A team admin turns on Microsoft Teams for the team first. Then the owner or a

252Manager connects the Bot from its details under **Bring to your team's

253Microsoft Teams**, and a Microsoft Teams admin approves it. The full steps,

254what the Bot can do there, and what to do when it isn't in Teams yet are on

255[Use Grok Bot in Microsoft Teams](/grok-bot/microsoft-teams).

256 

257## How do I edit or delete a Team Bot?

258 

259The owner and the Bot's Managers can change a Team Bot. Its details show in

260the panel on the right of the chat:

261 

262* **Plugins** (the Bot's connected apps), **Secrets**, **Skills**, and

263 **Files** hold what the Bot uses for everyone.

264* Click the name to rename the Bot. Edit the description under **About**.

265* **Share** controls who can use the Bot and who manages it.

266 

267Choose the wrench, **Manage**, for the rest:

268 

269* **General** has the Bot's settings, such as whether Collaborators can set up

270 routines, its channels such as Slack and Microsoft Teams, and the **Bot's

271 accounts** it signs in to apps with.

272* **Knowledge** shows what the Bot learned for everyone, and its skills. New

273 learnings wait under **To review** until you choose **Approve** or

274 **Reject**.

275* **Analytics**, when shown, has the Bot's messages, hours saved, and top users.

276 

277The owner can also rename the Bot by right-clicking it in the sidebar and

278choosing **Rename Bot**.

279 

280Only the owner can delete a Team Bot. Right-click the Bot in the sidebar and

281choose **Delete**. A team admin can also delete it from **Manage Bots** in the

282dashboard. This deletes the Bot for your whole team. Teammates lose it,

283along with their chats and routines on it. It can't be undone.

284 

285## How do I remove a Team Bot from my sidebar?

286 

287Right-click the Bot and choose **Remove from sidebar**. To add it back, choose

288**+** in the sidebar, then **Browse shared Bots**, and choose **Add** next to

289it.

290 

291If your admin added the Bot to your sidebar for you, **Remove from sidebar**

292isn't in its menu, and you can't remove it.

293 

294## Can I use Team Bots on my phone?

295 

296Yes. Team Bots you've added appear in the [phone app](/grok-bot/mobile). To

297find another, tap **+**, then **Browse shared Bots**. Each Bot in the list

298shows how many people use it, and **Add** keeps it in your list. You can chat

299with Team Bots and answer their **Allow** cards. A Team Bot can't be your

300[primary Bot](/grok-bot/bots#your-primary-bot).

301 

302To remove a teammate's Bot from your list, touch and hold it and choose

303**Remove from sidebar**.

304 

305The owner and Managers can also manage a Team Bot from its profile on the

306phone:

307 

308* **Share** opens **Share this Bot**, where you choose who has access and add

309 people. If you're on more than one team, choose a team before you share.

310* **Tools** has the Bot's service accounts, and **Slack** adds the Bot to Slack

311 with your own Slack connection. See [How do I add a Team Bot to

312 Slack?](#how-do-i-add-a-team-bot-to-slack)

313* **Skills** lists the Bot's skills. Tap **+** to choose **Add Custom Skill**

314 or **Import Existing Skill**, and open a skill to edit it and choose **Save

315 changes**.

316* **Learnings** shows how many learnings are waiting, for example "3 to

317 review". Choose **Approve** or **Reject** on each one.

318* **Routines** lists the Bot's routines, with **Add routine** and the

319 **Collaborators can create routines** switch.

320* **Analytics**, when shown, has weekly and daily active users, messages, hours

321 saved, and top users, over **7 days**, **30 days**, or **90 days**.

322 

323When you ask one of your own Bots on the phone to work with your team, it shows

324a **Team access** card. **Share** moves that Bot to the team with its chat and

325memories, or **Copy** makes a team copy and keeps the original private. **Start

326fresh** creates a new Team Bot without this chat or its memories.

327 

328## Can I voice chat with a teammate's Team Bot?

329 

330Yes, on desktop. In your own chat with the Bot, choose **Start voice chat**. See

331[Start a voice chat](/grok-bot/chat-and-collaboration#start-a-voice-chat).

332 

333## Can a Team Bot join a group chat?

334 

335Yes. You can add a Bot a teammate shared with you to your own group chat. It

336can't share a group with Bots that run on your own computer. See [Start a group

337chat](/grok-bot/chat-and-collaboration#start-a-group-chat).

338 

339## How do admins manage Team Bots?

340 

341On the Grok Bot page of the [Cursor dashboard](https://cursor.com/dashboard/bot),

342open **Manage Bots** under **Shared Bots**.

343 

344* **Access** shows who can use each Team Bot. Click it to change who can use

345 the Bot.

346* **Auto-add** puts the Bot in members' sidebars automatically. Pick **All

347 team** or one or more groups. Those members can't hide it. Auto-add only

348 applies to groups that have access.

349* Admins can also delete a Team Bot here.

350 

351Under **Sharing** on the same page:

352 

353* **Bot sharing** decides who may share Bots: **Everyone** or **Admins only**.

354 Bots already shared stay shared.

355* **Allow Shared Logins** lets Managers share their own app logins as [shared

356 connectors](#how-do-shared-connectors-work). Everyone who uses the Bot then

357 acts through that Manager's account. It's off by default.

358* **Slack Workspace Access** lets members of your Slack workspace who aren't on

359 the team use Bots shared with your organization. It's on by default, and in

360 an organization it applies to every team. The setting appears as it reaches

361 your team.

362 

363See [Grok Bot for teams and

364enterprises](/grok-bot/teams-and-enterprises#manage-bots).

365 

366## Why can't I see or use a Team Bot?

367 

368| What you see | What it means |

369| --- | --- |

370| **Browse shared Bots** isn't under **+** | You aren't on a Cursor team, or your Grok Bot app needs an update. |

371| **Team Bots Not Available** | Your account doesn't have access to Team Bots. |

372| **Only team admins can share Bots** | Your team admin limited Bot sharing to admins. **Share** is disabled, and the message appears when you hover it. Ask an admin to share the Bot for you, or to change **Bot sharing** on the team dashboard. |

373| **Bot Not Found** | The Bot may have been removed, or it isn't shared with you. |

374| **No Access to This Bot** | The Bot is shared only with certain people. Ask its owner or a Manager for access. |

375| A teammate's Bot isn't in **Browse shared Bots** | The owner hasn't shared it with you yet. |

376| **Your usage limit has been reached** | Your Grok Bot usage ran out. Your chats with a teammate's Team Bot use your usage. See [How much does Grok Bot cost?](/grok-bot/faq#how-much-does-grok-bot-cost) |

377| **This Bot's owner has reached their usage limit** | This reply was billed to the owner's account, and the owner's usage ran out. Ask the owner to check their plan. |

378| **This conversation can't run on your computer because your privacy mode is stricter than the bot owner's.** | Your privacy mode setting is stricter than the owner's, so this chat can't use your computer. |

379| In Slack, the Bot asks you to link a Cursor account | Link your Slack account under **Settings** > **General** > **Team Bots**, using the Cursor account on the Bot's team. |

380| In Slack, **some features will be limited** | The Bot answered you without a linked account. Link one so it knows who you are and can use your apps. |

381| In Slack, **I haven't been shared with you yet** | Ask the Bot's owner or a Manager to add you under **Share this Bot**. |

382| In Slack, the Bot says it's someone's personal Bot | Only its owner can talk to it. |

383| **Your admin has turned off sharing logins with Bots** | A team admin needs to turn on **Allow Shared Logins** before a Manager can share an account as a shared connector. |

384 

385If none of these match, [contact support](/grok-bot/troubleshooting) with the

386Bot's name, the exact message, and your Grok Bot version.

387 

388## Related pages

389 

390* [Use Grok Bot in Microsoft Teams](/grok-bot/microsoft-teams)

391* [Add a Bot to your meetings](/grok-bot/meetings)

392* [Create and manage Bots](/grok-bot/bots)

393* [Message and collaborate](/grok-bot/chat-and-collaboration)

394* [Use the computer and apps](/grok-bot/computer-and-apps)

395* [Vault and secure sign-in](/grok-bot/vault)

396* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

397* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

398* [Troubleshooting](/grok-bot/troubleshooting)

Details

131temporary files when work completes. When a workload needs its own computer and131temporary files when work completes. When a workload needs its own computer and

132credential set, give it its own Cursor user.132credential set, give it its own Cursor user.

133 133 

134[Shared Bots](/grok-bot/shared-bots) are the exception to one Bot per user. A134[Shared Bots](/grok-bot/team-bots) are the exception to one Bot per user. A

135Bot is either personal or shared: a member shares a cloud-hosted Bot with135Bot is either personal or shared: a member shares a cloud-hosted Bot with

136everyone on the team, or only with certain people and groups, and those members136everyone on the team, or only with certain people and groups, and those members

137can chat with it. Each member's chat is private, including from the owner and137can chat with it. Each member's chat is private, including from the owner and

138the Bot's Managers. In a member's own chat or Slack DM, the Bot usually works138the Bot's Managers. In a member's own chat or Slack DM, the Bot usually works

139on that member's computer, uses that member's connected accounts after asking,139on that member's computer, uses that member's connected accounts after asking,

140and uses that member's Grok Bot usage. In Slack channels, threads, group DMs,140and uses that member's Grok Bot usage. In Slack channels, threads, group DMs,

141and group chats, a shared Bot uses one computer of its own. Secrets, apps, and141and group chats, a Team Bot uses one computer of its own. Secrets, apps, and

142files the owner or a Manager adds to a shared Bot are available in every142files the owner or a Manager adds to a Team Bot are available in every

143teammate's chat.143teammate's chat.

144 144 

145## Admin controls145## Admin controls


206off; other teams start with it allowed. For what a shared template contains,206off; other teams start with it allowed. For what a shared template contains,

207see [Share a Bot](/grok-bot/bots#share-a-bot).207see [Share a Bot](/grok-bot/bots#share-a-bot).

208 208 

209#### Bot sharing

210 

211Controls who may share a Bot with teammates. Find **Bot sharing** under

212**Sharing** on the Grok Bot page and pick **Everyone** or **Admins only**.

213**Everyone** is the default. With **Admins only**, members see **Only team

214admins can share Bots** and the **Share** control is disabled for them; Cursor

215enforces this on its servers. Bots already shared stay shared, and the access

216an admin sets in **Manage Bots** still applies. See [Who can share

217Bots?](/grok-bot/team-bots#who-can-share-bots)

218 

219#### Allow Shared Logins

220 

221Lets a Team Bot's Managers share their own app logins as shared connectors.

222Find **Allow Shared Logins** under **Sharing** on the Grok Bot page. It's off

223by default. When it's on, everyone who uses the Bot acts through that Manager's

224account, including for changes the Bot makes. When it's off, Managers see

225**Your admin has turned off sharing logins with Bots**. See [How do shared

226connectors work?](/grok-bot/team-bots#how-do-shared-connectors-work)

227 

228#### Slack Workspace Access

229 

230Lets members of your Slack workspace who aren't on the team use Team Bots in

231Slack without a linked account. It applies to Bots shared with your

232organization, or with the team when it's the organization's only team or isn't

233in one. Their replies use the team's usage. Slack guests and Slack Connect

234channels are never included. Find **Slack Workspace Access** under **Sharing**

235on the Grok Bot page. It's on by default. In an organization, an organization

236admin sets it for every team. The setting appears as it reaches your team. See

237[Who can talk to a Team Bot in

238Slack?](/grok-bot/team-bots#who-can-talk-to-a-team-bot-in-slack)

239 

209#### Manage Bots240#### Manage Bots

210 241 

211Lists every Bot on your team. Open **Manage Bots** under **Shared Bots** on the242Lists every Bot on your team. Open **Manage Bots** under **Shared Bots** on the

212Grok Bot page, and filter the list by sharing or by owner. The **Access** column243Grok Bot page, and filter the list by sharing or by owner. The **Access** column

213shows who can use each [shared Bot](/grok-bot/shared-bots), such as the whole244shows who can use each [Team Bot](/grok-bot/team-bots), such as the whole

214team, certain people or groups, or only its owner. Click it to change who has245team, certain people or groups, or only its owner. Click it to change who has

215access. In a Bot's **Auto-add** column, pick **All team** or one or more groups246access. In a Bot's **Auto-add** column, pick **All team** or one or more groups

216to add the Bot to those members' sidebars, or clear it. Auto-add only applies to247to add the Bot to those members' sidebars, or clear it. Auto-add only applies to


222 253 

223#### Microsoft Teams254#### Microsoft Teams

224 255 

225Lets the team's shared Bots join Microsoft Teams. Under **Shared Bots** on the256Lets the team's Team Bots join Microsoft Teams. Under **Shared Bots** on the

226Grok Bot page, choose **Enable** next to **Enable Microsoft Teams** and sign in257Grok Bot page, choose **Enable** next to **Enable Microsoft Teams** and sign in

227with a Microsoft Teams or Global administrator account. The row then shows258with a Microsoft Teams or Global administrator account. The row then shows that

228**Microsoft Teams enabled for** your organization, and **Revoke** turns it off.259Microsoft Teams is enabled for your organization, and **Revoke** turns it off.

229Only team admins can enable it. A Microsoft Teams admin still approves each Bot260Only team admins can enable it. A Microsoft Teams admin still approves each Bot

230in the Teams admin center. **Manage Microsoft Teams accounts** lists the members261in the Teams admin center. **Manage Microsoft Teams accounts** lists the

231who linked a Microsoft Teams account. See [How do I add a shared Bot to Microsoft262members who linked a Microsoft Teams account, and lets you unlink one. See [Use

232Teams?](/grok-bot/shared-bots#how-do-i-add-a-shared-bot-to-microsoft-teams)263Grok Bot in Microsoft Teams](/grok-bot/microsoft-teams).

264 

265#### Meetings

266 

267Controls whether members' Bots can join Google Meet, Zoom, and Microsoft Teams

268calls, transcribe them, and report back. The **Meetings** switch is under **Bot

269Capabilities** on the Grok Bot page. Meetings are available on Team,

270Enterprise, and Ultra plans. Enterprise admins can turn on Meetings here. When

271it's off, Bots can't join or read meetings. A Team Bot joins meetings only when

272its own team allows them. See

273[Add a Bot to your meetings](/grok-bot/meetings).

233 274 

234#### Page sharing275#### Page sharing

235 276 


351 392 

352Restricts which destinations team computers can reach. Find it under393Restricts which destinations team computers can reach. Find it under

353**Network** on the Grok Bot page as **Grok Bot Network Access**. Pick394**Network** on the Grok Bot page as **Grok Bot Network Access**. Pick

354**Allow All Network Access**, **Defaults + Team Allowlist**, or395**Allow All Network Access**, **Allow All Sites Except These**,

355**Team Allowlist Only**, and list domains and IP ranges for the allowlist396**Defaults + Team Allowlist**, or **Team Allowlist Only**. List domains and IP

356modes. Directory groups can carry their own policy, and a lock makes the team397ranges for the allowlist modes, or the sites to block under **Blocked Sites**.

357policy apply to everyone. Teams without a policy default to allow-all. See398Directory groups can carry their own policy, and a lock makes the team policy

399apply to everyone. Teams without a policy default to allow-all. See

358[network policy](/grok-bot/security#network-policy) for the modes and how a400[network policy](/grok-bot/security#network-policy) for the modes and how a

359new policy reaches running computers.401new policy reaches running computers.

360 402 

403**Allow All Sites Except These** lets computers reach everything except the

404sites you list. Enter one hostname per line, such as `example.com`, with no

405scheme, port, or path. Each site also blocks its subdomains. A team and its

406groups can block up to 50 sites in all. Blocking works on a best-effort basis

407and is not a security boundary. See

408[Blocked sites](/grok-bot/security#blocked-sites) for what it covers and its

409limits.

410 

361In an allowlist mode, the **Apply to MCP servers** switch appears below the411In an allowlist mode, the **Apply to MCP servers** switch appears below the

362destination list. It is off by default. When it is on, every connected app,412destination list. It is off by default. When it is on, every connected app,

363including built-in connectors such as GitHub, X, and Origin, must match an413including built-in connectors such as GitHub, X, and Origin, must match an


544 members, whether looser or tighter, and a member of several groups gets the594 members, whether looser or tighter, and a member of several groups gets the

545 most restrictive one. A locked team policy applies to everyone.595 most restrictive one. A locked team policy applies to everyone.

546 **Apply to MCP servers** is set on the team's Grok Bot page only; a group596 **Apply to MCP servers** is set on the team's Grok Bot page only; a group

547 inherits it and cannot turn it off.597 inherits it and cannot turn it off. Blocked sites add up instead: pick

598 **Team Policy, Except These Sites** to block more sites for group members on

599 top of the team policy. Sites the team blocks stay blocked for group

600 members, whatever the group sets, and sites a group blocks stay blocked even

601 when the team policy is locked.

548* **Group Rules.** Rules for the group's Bots, combined with602* **Group Rules.** Rules for the group's Bots, combined with

549 [Team Rules](#team-rules). Members cannot turn them off.603 [Team Rules](#team-rules). Members cannot turn them off.

550* **Setup Scripts.** Manifests that run on group members' computers alongside604* **Setup Scripts.** Manifests that run on group members' computers alongside

vault.md +3 −3

Details

28 28 

29Vault covers your whole account: everything you save is available to every Bot29Vault covers your whole account: everything you save is available to every Bot

30on your account, and you can't limit an item to one Bot. Your Vault isn't30on your account, and you can't limit an item to one Bot. Your Vault isn't

31available on [shared Bots](/grok-bot/shared-bots): a shared Bot can't use the31available on [shared Bots](/grok-bot/team-bots): a shared Bot can't use the

32logins, cards, or contact info you saved. Add keys to a shared Bot under32logins, cards, or contact info you saved. Add keys to a shared Bot under

33**Secrets** instead. See [API keys and other33**Secrets** instead. See [API keys and other

34secrets](#api-keys-and-other-secrets).34secrets](#api-keys-and-other-secrets).


137securely**, and the card then says **Saved** and **Saved securely and kept137securely**, and the card then says **Saved** and **Saved securely and kept

138private**. The value isn't written into the chat or shown to the Bot.138private**. The value isn't written into the chat or shown to the Bot.

139 139 

140On a [shared Bot](/grok-bot/shared-bots) you own or manage, you can also add a140On a [shared Bot](/grok-bot/team-bots) you own or manage, you can also add a

141secret from the Bot's details. Open **Secrets**, choose **Add secret**, enter an141secret from the Bot's details. Open **Secrets**, choose **Add secret**, enter an

142environment variable name, a short description, and the value, then choose142environment variable name, a short description, and the value, then choose

143**Save secret**. The description is visible to the Bot; the value is not.143**Save secret**. The description is visible to the Bot; the value is not.


239## Related pages239## Related pages

240 240 

241* [Use the computer and apps](/grok-bot/computer-and-apps)241* [Use the computer and apps](/grok-bot/computer-and-apps)

242* [Shared Bots](/grok-bot/shared-bots)242* [Shared Bots](/grok-bot/team-bots)

243* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)243* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

244* [Store secrets securely](https://cursor.com/help/grok-bot/secrets)244* [Store secrets securely](https://cursor.com/help/grok-bot/secrets)