Grok Bot shared Bots: give your team one Bot, pick who manages it, and know whose usage pays

Disclosure: aitamer.news is produced with Grok Bot and Cursor, two of the products covered in this tutorial.

Earlier episodes called it a Team Bot. The help pages now call it a shared Bot, and you now pick who gets it and who manages it. You share a Bot with your Cursor team the way you would share a doc: with the whole team, or only with the people and groups you pick. Sharing makes no copy. Everyone talks to the same Bot, and each person’s chat with it stays private.

That idea, one Bot and many private chats, explains most of what follows. Episode 05 built a roster of personal Bots; this is the Bot you build once for everyone.

The main sources are the Cursor help page on shared Bots and the matching SpaceXSI page, both read 3 November 2026. If a menu or label below disagrees with your app, follow the app.

Who can use them

Shared Bots are for members of a Cursor team who have Grok Bot. Choose + in the sidebar. If you see Create a Bot and Browse shared Bots, you are set. If Browse shared Bots is missing, either you are not on a Cursor team or your Grok Bot app needs an update.

Two limits. A shared Bot always runs in the cloud, so a Bot that runs on your own computer can’t be shared. And on a phone, sharing and browsing need Grok Bot 1.19.0 or later on iPhone or Android. Older versions still open the shared Bots already in your list, and some of their screens still say Team Bots.

Make one, or share one you have

To start fresh, choose +, then Create a Bot, name it, tell it in a sentence what it should help the team with, and follow its setup steps.

You can also share a Bot you already run. Sharing doesn’t duplicate it, so whatever it holds goes with it. Both help pages give the same warning: before you share, check its apps, secrets, skills, and files, because they work in every teammate’s chat. Only add keys and files you are happy for everyone you share with to use.

Share it, and choose roles

Click the Bot’s name at the top of the chat and choose Share. In Share this Bot:

• Under Who has access, pick your team to share with everyone, or People you invite to share only with the people and groups you add. Limiting access asks you to confirm with Limit access.
• Choose Add people or groups. Under Add as, pick Collaborator to let someone chat with the Bot, or Manager to let them also change how it works: its instructions, skills, memory, and apps.

The owner and Managers can always use the Bot. To stop sharing, open Share again and remove access.

Keep Managers few: they change what every chat runs on.

How teammates find it

Teammates choose +, then Browse shared Bots, on desktop or phone. The list shows each Bot shared with them and who made it, and Add keeps one in the sidebar. A teammate’s link works too: open it and choose Start a chat.

Don’t mix this up with a template. A shared Bot’s link opens the same Bot for everyone; a template link, per the Cursor docs, gives each person their own copy, without your computer, logins, or history. Episode 10 covers templates.

What stays private

Each person’s chat with a shared Bot is private. The owner and Managers can’t read your chats, and you can’t read theirs.

Memory is split the same way. The Bot can save things it learns for the whole team, and it tells you when it does. It doesn’t save anything about you personally for the team. What it remembers about working with you stays between you and the Bot.

Whose apps, and which computer

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, but it asks first. The card says Allow and the app name:

• Allow once uses that account this time.
• Always allow remembers your answer. Its menu offers Always allow for your messages to this Bot and Always allow for your messages to every Shared Bot.
• Skip leaves that account out this time.

A connected account always acts as the person the Bot is answering. One teammate’s connection is never used for someone else. In Slack channels, threads, and group chats, a shared Bot uses only its owner’s apps and asks before it uses yours. To make every shared Bot ask again, open Settings > General > Shared Bots and choose Clear next to Clear connector preferences.

The computer splits the same way. In your own chat, or a Slack DM, the Bot usually works on your Grok Bot computer, with your files and the sites you are signed in to there; 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.

Who pays, and who approves

A shared Bot reply uses the Grok Bot usage of the person it is answering, in your own chat, in Slack, and in group chats, and your own limits apply. 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.

Approvals follow the same person. A shared Bot asks the person it is answering before risky actions. In your own chat, you answer its approval cards. In a Slack thread it posts a Review an action card with Allow once, Deny, and View details, and only the person who asked can answer. In a group chat, only the person whose message the Bot is answering can answer. Episode 09 shows where gates like these fit in a team setup.

Slack, phones, and groups

The owner or a Manager brings a shared Bot to Slack after sharing it: click the Bot’s name, find Bring to your team’s Slack, and choose Connect. Awaiting admin approval means a Slack workspace admin has to approve the app. Each teammate first links their Slack account under Settings > General > Shared Bots with Link.

Shared Bots you added also appear in the phone app, where you can chat and answer their Allow cards, but a shared Bot can’t be your primary Bot. You can add one to your own group chat, though not alongside Bots that run on your own computer.

Editing, hiding, and deleting

The owner and Managers can change a shared Bot: click its name for its details, or the wrench at the top right for Bot settings, where Plugins, Secrets, Skills, and Files hold what it uses for everyone.

Only the owner can delete a shared Bot from the sidebar, and it is final: it deletes the Bot for the whole team, with teammates’ chats and routines on it, and can’t be undone. Anyone else can right-click it and pick Hide from sidebar, unless an admin added it for them.

What admins control

On the Grok Bot page of the Cursor dashboard, Manage Shared Bots under Shared Bots has an Access column to change who can use each Bot, and Auto-add to put a Bot in the sidebars of the whole team or chosen groups. Members who get a Bot that way can’t hide it, and Auto-add only applies to groups that have access. The SpaceXSI teams page adds that admins can delete one there too, which also removes its Slack app.

When it doesn’t work

The pages share a short table. In brief:

• No Access to This Bot: it is shared only with certain people. Ask the owner or a Manager.
• Your usage limit has been reached: your own usage ran out, since your chats use your usage.
• This Bot’s owner has reached their usage limit: this reply was billed to the owner, and their usage ran out.

A first shared Bot, step by step

1. Pick one job the team asks about every week, and create a Bot for it.
2. Add only the apps, secrets, skills, and files everyone may use.
3. Share it with People you invite first: a few Collaborators, one Manager.
4. Have them try it in their own chats, then widen access to the team.

After that, the team has one Bot to ask, each chat stays private, and each person’s usage covers their own replies.