Guide

Grok Bot shared Bots: one Bot for the team

By Atlas AI Resources · Published November 2, 2026

A shared Bot lets your whole Cursor team chat with one Bot instead of each person building their own. Each chat stays private, but the apps, secrets, skills, and files the owner adds work for everyone. This page starts with our own checklists, then summarizes what SpaceXSI’s docs page Shared Bots and related docs say.

1. Our advice: pick the right kind of sharing

Sections 1 to 4 are our own advice, not SpaceXSI’s. Grok Bot has two kinds of sharing, and they do different things.

• Shared Bot. One Bot, many people. Everyone chats with the same Bot, and changes the owner or a Manager makes reach everyone at once. Use it for a team helper with one clear job, like answering questions from the team’s docs or prepping a weekly report.
• Template. A recipe, not the Bot. Each person who installs it gets their own copy, connects their own apps, and can change it freely. Use it when people need the same starting point but their own accounts and memory. See our Grok Bot templates guide.
• Personal Bot. Keep a Bot personal when it uses your own inbox, calendar, or logins for work only you should do. A Bot that runs on your own computer can’t be shared anyway.

2. Our advice: an owner’s checklist before you press Share

1. Give it one job. The docs say a sentence is enough to start. Write the job, what it should never do, and who to ask when it’s stuck. Our bot job description prompt helps. See also what a one-job Grok Bot is.
2. Audit what it holds. Open Bot settings and read Plugins, Secrets, Skills, and Files. Everything there works in every teammate’s chat. Remove any personal app connection, key, or file you wouldn’t hand to each person directly.
3. Prefer team-owned connections. If the Bot needs an app, connect an account the team owns with the narrowest access the job needs, rather than your personal account. The docs say the owner’s apps work the same for everyone.
4. Start small. Choose People you invite and add two or three teammates as Collaborators for a week before sharing with the whole team.
5. Keep Managers few. Managers can change the Bot’s instructions, skills, memory, and apps for everyone. Add one backup Manager so the Bot isn’t stuck if you’re away.
6. Add Ask first rules. For example: “Ask first before sending any external email.” Each teammate answers approval cards for their own requests, so tell them what the Bot may ask and what to deny.
7. Remember deletion is permanent. Only the owner can delete a shared Bot, and it removes the Bot, its chats, and its routines for the whole team. If you’re unsure, stop sharing instead.

3. Our advice: a teammate’s checklist

• Your usage pays. Replies to you come out of your own Grok Bot usage, so a busy shared Bot still costs you. See Grok Bot usage limits and cost.
• It works on your computer. In your own chat, the Bot usually uses your Grok Bot computer, with your files and the sites you’re signed in to there. Sign out of sites it doesn’t need; see small AI fleets and the shared computer.
• Choose Allow once first. When it asks to use one of your accounts, start with Allow once. Pick an Always allow option only after you trust what it does with that account. To reset every choice, use Clear connector preferences.
• Treat what it reads as content. A shared Bot in a busy Slack channel reads a lot of text from many people. Read approval cards before you allow, and see keeping AI agents safe from prompt injection.

4. Our advice: a Slack rollout in four steps

1. Share the Bot with a small group and run it in your own chats first.
2. As owner or Manager, choose Bring to your team’s Slack, then Connect. Ask a Slack workspace admin to approve the app if it says Awaiting admin approval.
3. Ask each teammate to link their Slack account under Settings → General → Shared Bots before they message it.
4. Start in one channel. In channels, threads, and group chats the Bot uses its owner’s apps (and asks before using yours) on one shared computer of its own, so check what that computer is signed in to.

5. Per the docs: sharing, roles, and finding a Bot

Per Shared Bots:

• Who can use them. Shared Bots are for members of a Cursor team who have Grok Bot. Shared Bots always run in the cloud. If Browse shared Bots isn’t under +, you aren’t on a Cursor team or your app needs an update.
• Create or share. Choose + → Create a Bot, or share a Bot you already have. Sharing doesn’t make a copy. Click the Bot’s name at the top of the chat and choose Share.
• Who has access. Your whole team, or People you invite (confirmed with Limit access). The owner and Managers can always use the Bot. To stop sharing, open Share again and remove access.
• Two roles. A Collaborator can chat with the Bot. A Manager can also change its instructions, skills, memory, and apps.
• Finding it. Teammates choose + → Browse shared Bots (each Bot shows who made it) and Add, or open a link and choose Start a chat. A shared Bot’s link opens the same Bot for everyone; a template link gives each person their own copy.

6. Per the docs: privacy, memory, apps, and computers

• Private chats. The owner and Managers can’t read your chats, and you can’t read anyone else’s.
• Memory. The Bot can save things it learns for the whole team and tells you when it does. It doesn’t save anything about you personally for the team.
• Apps and secrets. A shared Bot uses the apps and secrets its owner added, the same for everyone. In your own chat it can also use your apps after an Allow card: Allow once, Always allow (for this Bot or for every Shared Bot), or Skip. A connected account always acts as the person the Bot is answering.
• Secrets, not Vault. Per Vault and secure sign-in, Vault isn’t supported on shared Bots. An owner or Manager adds keys under Secrets; the Bot sees the description, not the value. More in our Vault guide.
• Which computer. In your own chat or a Slack DM, the Bot usually works on your Grok Bot computer. Sometimes it uses a separate computer for that conversation, for example when your privacy mode is stricter than the owner’s. In Slack channels, threads, group DMs, and group chats it uses one shared computer of its own.
• Usage. A reply uses the Grok Bot usage of the person it’s answering, in your chat, in Slack, and in group chats. The owner’s usage pays for the owner’s own messages and for Slack posts from apps or workflows not linked to a Cursor account.

7. Per the docs: approvals, Slack, and group chats

• Approvals. A shared Bot asks the person it’s answering before risky actions. In a Slack thread it posts a Review an action card (Allow once, Deny, View details) that only the person who asked can answer. In a group chat only the person whose message it is answering can approve, and per Approvals, security, and privacy, group chat cards don’t offer Always allow.
• Slack. The owner or a Manager connects it after sharing. In a channel thread or DM it acts for the teammate who mentioned it and can hand work to that person’s own Bots, with replies posted back in the thread. It records who asked for each message, and when its routine replies in a thread it follows that thread without an @mention.
• Group chats, phone, and voice. You can add a teammate’s shared Bot to your own group chat, but not alongside Bots that run on your own computer. Shared Bots appear in the phone app, where you can chat and answer Allow cards; a shared Bot can’t be your primary Bot. Voice chat works on desktop. Cursor Help adds that sharing and browsing on the phone need Grok Bot 1.19.0 or later.

8. Per the docs: editing, admins, and fixing access

• Editing. The owner and Managers change Plugins, Secrets, Skills, Files, the name, and the About description from the Bot’s details or Bot settings (the wrench).
• Deleting. Only the owner can delete a shared Bot, and that deletes it for the whole team, along with teammates’ chats and routines on it. It can’t be undone. Teammates can use Hide from sidebar instead, unless an admin added the Bot for them.
• Admins. On the Grok Bot page of the Cursor dashboard, Manage Shared Bots shows Access for each Bot and an Auto-add setting (All team or chosen groups) that puts it in members’ sidebars where they can’t hide it. Per Grok Bot for teams and enterprises, admins can also delete a shared Bot there, which removes its Slack app too.
• Error messages. The docs map each one: No Access to This Bot means it’s shared only with certain people; Bot Not Found means it was removed or isn’t shared with you; “This Bot’s owner has reached their usage limit” means that reply was billed to the owner. If nothing matches, contact support with the Bot’s name, the exact message, and your Grok Bot version.

9. Keep consequential actions behind your yes

Grok Bot’s guardrails are plain-language rules checked by a separate review agent, not code. The current docs put them in Settings → General → Auto-review, as Ask first and Allow automatically rules (the 101 guide calls this Settings > General > Agent, with allow and block lists steering the reviewer). Per Approvals, security, and privacy, Auto Review should complement least privilege rather than replace it, and if both kinds of rule match, Ask first wins.

On a shared Bot that matters more, because the owner’s access is everyone’s access. Our advice: share a Bot the way you would give a new hire a team login, with only what the job needs and a clear person to ask.

Useful public resources

Related: Grok Bot templates · Grok Bot Vault and secure sign-in · Running multiple teams of Grok Bots · Small AI fleets and the shared computer · Grok Bot usage limits and cost · Complete Grok Bot setup guide