Grok Bot Teams: Set Up A Shared Bot In 6 Steps (2026)

Grok Bot teams is the setup where you build one Bot, share it with your team, and every teammate chats with it in their own private conversation.

It first appeared under the name Team Bots in release v0.61.0, dated 26 September 2026, and the current docs call the same thing Shared Bots.

I'd set it up in six steps: create, load, share, add Managers, connect Slack, then link every teammate.

Below is each step with the exact menu names, plus the admin settings and gotchas that trip people up.

If you'd rather plan the rollout with someone, book a free SEO strategy session with my team and we'll map it with you.

Team Bots became Shared Bots: what the rename means for setup

The feature didn't change shape when the name changed.

In v0.78.1 (27 October 2026) the admin page started saying "Shared Bots", with Manage Shared Bots and Create Bot on it.

Older changelog lines still say "Team Bot", "Publish to team" and "Manage team bots".

Read them as the same feature.

One thing is fixed either way: sharing only works for cloud-hosted Bots.

Anything you've set to run locally stays personal, so build the team Bot as a cloud Bot from the start.

Before you start: check these four things

You're on a Cursor team. The Shared Bots page limits sharing to Grok Bot users inside a Cursor team.
Your plan includes Grok Bot. Under The X Subscription, Premium, Super and Ultra include it, and Plus doesn't. On the Cursor Teams plan it's on by default for every member.
Your app is current. If Browse shared Bots is missing under +, you're either off a team or your app needs an update.
Privacy Mode (Legacy) is off. The teams and enterprises docs say that setting blocks Grok Bot entirely.

Fix whichever one fails before you touch the Bot.

Step 1: Create the Bot from the + menu

Choose + in the sidebar.
Pick Create a Bot and give it a name your team will recognise, such as "Ops Desk".
Tell it what it helps the team with in one sentence.

One sentence really is enough at this stage.

I'd write the job as an outcome: "Answer supplier and order questions for the ops team, and draft replies for review."

The Bots docs push the same idea: give one Bot ownership of an end-to-end outcome before you add a second.

Step 2: Load apps, secrets, skills and files you'd give anyone

The Bot walks you through its setup steps for apps, secrets, skills and files.

The v0.61.0 notes describe it as one card at a time, and only you see the Bot until you share it.

This is the step that decides what every teammate can reach.

Apps, secrets and files the owner or a Manager adds work in every teammate's chat.

So my rule is simple: if I wouldn't paste it into the team channel, it doesn't go on the shared Bot.

Secrets: open Secrets, choose Add secret, then enter an environment variable name, a description and the value. The Vault docs say the Bot sees the description, never the value.
Logins: since v0.78.1, Managers can add logins to the Bot's own Vault under Configure > Tools.
Files: add the reference docs the whole team needs, like a price list template or a returns policy.
Skills: attach only the skills the job sentence calls for.

🔥 Want the shared-Bot setup done with you, not guessed? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members building agent teams. → Join the AI Profit Boardroom

Step 3: Share it and choose who has access

Click the Bot's name at the top of the chat and choose Share.

In Share this Bot, go to Who has access:

Pick your team to open it to everyone.
Pick People you invite to limit it to named people and groups. You confirm with Limit access.
Since v0.78.1, you can also limit a Team Bot to Only you.

I'd start with People you invite and two or three testers.

Widen it to the whole team once the Bot answers the first ten real questions well.

The owner and Managers can always use the Bot, whatever you pick here.

And since v0.75.8, anyone not on the share list has no access until an owner shares it, teammates included.

Step 4: Add Managers and keep everyone else a Collaborator

Inside Share, choose Add people or groups, then pick a role under Add as.

Role	Chats with it	Edits it	Deletes it
Owner	Yes	Everything, including sharing	Yes, for the whole team
Manager	Yes	Instructions, skills, memory and apps; plugins, secrets, skills, files and Share in Bot settings	No
Collaborator	Yes	No	No

Managers arrived in v0.64.0 on 30 September 2026.

I'd give Manager to one backup person, not to every senior teammate.

Every Manager can change what the Bot does for the whole team.

Since v0.75.2, owners and Managers can also let Collaborators create routines from Configure, so you don't need to hand out Manager just for that.

Step 5: Bring the Bot into Slack

The owner or a Manager connects Slack after sharing.

Click the Bot's name at the top of the chat.
Find Bring to your team's Slack and choose Connect.
If it says Awaiting admin approval, a Slack workspace admin approves the app.

Once it says Connected, teammates can DM the Bot or mention it in channels.

The chat and collaboration docs add that a shared Bot gets its own Slack app and handle.

In a channel thread, it acts for whoever mentioned it, and it can hand work to that person's own Bots.

Its replies land back in the same thread.

Two Slack details are worth knowing early:

Since v0.68.1, a Team Bot can mention a Slack user group, while @here and @channel still don't ping anyone.
Since v0.75.5, when its routine replies in a thread, the Bot follows that thread and answers later replies without an @mention.

Step 6: Get every teammate linked and chatting

Each teammate links their Slack account under Settings > General > Shared Bots and chooses Link.

If they message the Bot first, it replies with the linking steps anyway.

Linking matters more than it looks.

An unlinked teammate is locked out of the owner's saved sign-ins and private data, a guard added in v0.77.0.

In the app, teammates choose +, then Browse shared Bots, then Add.

The fastest path is a link: send it in Slack, they open it and choose Start a chat.

That link opens the same Bot for everyone, which is different from a template link that hands each person a copy.

How private chats and per-person notes actually work

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.

The Bot can save what it learns for the whole team, and it tells you when it does.

What it learns about working with you stays between you and the Bot, which is the "private notes per person" line from v0.61.0.

That split is useful for setup.

Team facts, like "we ship on Tuesdays", should end up in team memory.

Personal preferences, like "keep my drafts short", stay in that one teammate's notes.

Since v0.77.0, linked teammates also use their own connectors and memory on a Team Bot.

Whose allowance pays for each reply

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

App chat, Slack thread or group chat, the rule doesn't change.

The owner only pays for what the owner sends, and for posts that unlinked Slack apps or workflows trigger.

So an unlinked Slack workflow that pings the Bot all day lands on the owner.

I'd link or remove those workflows before going team-wide.

If a teammate sees Your usage limit has been reached, their own usage ran out.

If they see This Bot's owner has reached their usage limit, the reply was billed to the owner.

You can't set a Grok Bot-only budget yet, per the teams page, so lean on account-level on-demand controls.

📞 Rolling a shared Bot out to a whole team this month? Book a free SEO strategy session and we'll map which apps, logins and channels belong on it. → Book my free strategy session

The admin controls I'd set on day one

Admins work from the Grok Bot page of the Cursor dashboard, which members never see.

Under Shared Bots, open Manage Shared Bots:

Access shows who can use each shared Bot. Click it to change that.
Auto-add puts a Bot in sidebars for All team or chosen groups. Members can't hide a Bot added this way.
Admins can delete a shared Bot here too, which also removes its Slack app.

Then I'd set three more things on the same page.

Team Rules. Short rules every member's Bots follow, like "never move company data to personal accounts".
Execution on Local Computer. Pick Never allow unless a Bot really needs member machines.
Page sharing. Choose Anyone on the team, Specific teammates or Off.

On Enterprise, add Enforce Auto-review and team Ask first rules for payments, external email and production changes.

Without that lock, a shared Bot working in a chat with no one around to approve skips Auto-review, which is why I'd switch it on first.

Gotchas, with the fix for each

"No Access to This Bot": it's shared only with certain people. Ask the owner or a Manager to add you.
"Bot Not Found": it was removed, or it isn't shared with you.
Privacy mode message: your privacy mode is stricter than the owner's, so that chat can't run on your computer.
An app shows "Disabled by team admin": the team connector policy blocks it. An admin enables it in the Team Marketplace.
A teammate wants to leave the Bot: right-click and choose Hide from sidebar, unless an admin auto-added it.

One gotcha is permanent.

Hit Delete and every teammate loses the Bot, plus their conversations and routines on it, with no way back.

If you only want to change who can use it, edit Share instead.

Approvals on a shared Bot: who answers what

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

In Slack, it posts a Review an action card with Allow once, Deny and View details, and only the person who asked can answer.

When it wants one of your personal accounts, the card offers Allow once, Always allow or Skip.

I'd tell the team to use Allow once for anything touching money, accounts or shared resources, which is also what the recommended configuration says.

To make every shared Bot ask again, go to Settings > General > Shared Bots and choose Clear next to Clear connector preferences.

My rollout order for week one

Day 1: create the Bot, write the job sentence, add files and one app.
Day 2: share with People you invite and two testers. Add one Manager.
Day 3: connect Slack and get testers linked.
Day 4: read what went wrong, tighten instructions, set Team Rules.
Day 5: open it to the team and turn on Auto-add for the group that needs it.

Start read-only.

The docs recommend new roles begin with read-only tasks and drafts, with sending, publishing, purchasing and deletion kept behind approval.

That's exactly how I'd run the first week.

If you want the training, the Agent OS and live help while you build it, join the AI Profit Boardroom.

Also On Our Network

FAQ: Grok Bot Teams

Where do I find Browse shared Bots in Grok Bot?

Choose + in the sidebar. If Browse shared Bots isn't there, you aren't on a Cursor team or your Grok Bot app needs an update.

Can I share a Bot that runs on my own computer?

No. Shared Bots always run in the cloud, so a Bot running on your own computer can't be shared.

Who can add a shared Bot to Slack?

The owner or a Manager, after sharing. They click the Bot's name, find Bring to your team's Slack and choose Connect, and a Slack admin may need to approve the app.

What does a Manager do that a Collaborator can't?

A Collaborator can only chat with the Bot. A Manager can also change its instructions, skills, memory and apps, and edit plugins, secrets, files and sharing in Bot settings.

How do I stop a shared Bot remembering my app choices?

Open Settings > General > Shared Bots and choose Clear next to Clear connector preferences. Every shared Bot then asks again.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Build the Bot today, share it with two testers tomorrow, and book a free strategy session if you want help rolling out Grok Bot teams across your whole company.