Grok Bot sharing is a four-stage job: build a Team Bot in draft, publish it, open Share this Bot to set access and roles, then hand out the link while the admin settings decide who else may share.
This guide is the operator version: every menu name, every confirm dialog, every error string the docs list, and the settings that bite you later.
All of it comes from xAI's Team Bots documentation, the teams and enterprises admin page and the v1.0.1 changelog from 11 November 2026.
For the roles-and-dashboard overview, the Grok Bot teams guide covers it; this page is about the sharing itself.
Wiring Team Bots into a client's workflow? Book a free SEO strategy session and my team will map the first shared Bot with you.
Preflight: the four conditions that block sharing
Run these checks before you touch the Share button, because each one silently removes it.
- Plan. Team Bots exist on the Team and Enterprise plans only, for members who have Grok Bot.
- Headcount. The team needs at least one other member. A solo team can't create or share a Team Bot until someone joins.
- Location. Team Bots always run in the cloud. A Bot running on your own computer can't be shared.
- App version. If Browse shared Bots doesn't appear under +, either you aren't on a Cursor team or the app is out of date.
Phones have their own floor: sharing and browsing from iPhone or Android need Grok Bot 1.19.0 or later. Older builds still open Team Bots already in your list.
Some screens still say "shared Bots". The docs confirm that's the same thing as a Team Bot.
Stage 1: build the Bot as a private draft
- Sidebar + → Create a Bot → name it.
- Write its job in one line, for example "Drafts the weekly status email from Linear and Notion".
- Walk through its setup prompts for apps, secrets, skills and files.
Treat step 3 as a permissions decision, not a convenience step.
A Team Bot uses the apps and secrets its owner added, and those work the same for everyone who chats with it.
So an API key you paste here becomes usable by every teammate you later share with. Use scoped, team-safe keys only.
The draft is invisible to everyone but you. Run two or three real tasks through it before you go further.
Stage 2: publish, or promote a Bot you already run
When the Bot reports it's ready to share, hit Publish. It becomes discoverable to teammates from that point.
You can also share an existing Bot instead of building fresh. Sharing doesn't duplicate it, so audit its apps, secrets, skills and files first.
The mobile app gives three promotion paths through a Team access card when you ask one of your own Bots to work with your team:
- Share moves that Bot to the team, chat and memories included.
- Copy creates a team copy and keeps the original private.
- Start fresh creates a new Team Bot with none of the old chat or memories.
For a Bot with months of personal context in it, Copy or Start fresh is the safer pick.
🔥 Want shared Bots set up without trial and error? 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 AI teammates for real businesses. → Join the AI Profit Boardroom
Stage 3: the Share this Bot panel, field by field
Open Share at the top right of the Bot's chat.
Who has access
- Your team: everyone on the Cursor team.
- Your organization: everyone in the organization, if your team sits inside one.
- People you invite: only the people and groups you add. Switching to this asks you to confirm with Limit access.
- Only you: stops sharing. Confirm with Remove and everyone else drops off.
Add people or groups
Search a name or group. Anyone added lands as a Collaborator, which means chat access.
Open their role in the access list and switch it to Manager to let them change how the Bot works and share it with others. To cut one person, open their role and pick Remove.
Copy link
Copies a direct link to the Bot. It opens the same Bot for everyone, not a copy.
The owner and every Manager keep access no matter which option you set.
Roles you'll assign while sharing
| Role | Can chat | Can change the Bot | Can share it | Can delete it |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes (only the owner) |
| Manager | Yes | Yes | Yes | No |
| Collaborator | Yes | No | No | No |
| Team admin | If given access | Access and Auto-add | Controls Bot sharing | Yes, from Manage Bots |
Keep Managers to one or two people. Every Manager can also approve team learnings and change the Bot's apps.
Stage 4: distribution channels after you share
A link isn't the only way in. Teammates can reach a shared Bot through:
- Sidebar + → Browse shared Bots, which lists each Bot with its creator; Add pins it.
Cmd/Ctrl+Kin the desktop app → Browse shared Bots, sorted with Popular first and searchable.- Asking one of their own Bots, which searches the Team Bots they can use by what each does.
- The phone's + → Browse shared Bots, which also shows how many people use each one.
- A pasted link, followed by Start a chat.
Admins can skip all of that with Auto-add in Manage Bots, picking All team or specific groups. Auto-added Bots can't be hidden by members, and Remove from sidebar disappears from their menu.
The Bot sharing switch: Everyone vs Admins only
On the Grok Bot page of the Cursor dashboard, under Sharing, the Bot sharing setting has two values.
- Everyone: the default. Any team member can share.
- Admins only: members see a disabled Share button with the hover text Only team admins can share Bots. Cursor enforces this on its servers.
Flipping it doesn't unshare anything. Bots already shared stay shared, and access set in Manage Bots still applies.
The admin docs' recommended configuration calls for Admins only when Team Bots should be reviewed before teammates use them. That's my default for any team handling client data.
Shared connectors and Allow Shared Logins
By default a connected account acts as the person the Bot is answering, and one teammate's connection is never used for someone else.
A shared connector changes that for one app. Path: Bot details → Setup → Service accounts → pick the app under Shared connectors.
- Use individual accounts: each teammate connects their own.
- Share your account: everyone acts through your login, including writes. Connect it for yourself first.
- The Bot's own account: a separate account for the team. Some apps don't support it yet.
Share-your-account is gated by Allow Shared Logins, off by default. While it's off, the Bot replies Your admin has turned off sharing logins with Bots.
The changelog for v1.0.1 confirms owners and Managers gained this option once an admin enables the setting. Gotcha: if the shared app needs reconnecting, only the Manager whose account it is can do it.
What a teammate's session looks like
- Private chat. Owners and Managers can't read it.
- Their computer. In their own chat, the Bot usually works on the teammate's Grok Bot computer, with the files and sign-ins there. A stricter privacy mode than the owner's moves it to a separate computer.
- Their accounts, on request. The Bot asks before using a personal account: Allow once, Always allow, or Skip.
- Their usage. Replies draw on the usage of the person being answered.
- Their approvals. Risky actions prompt the asker, not the owner.
To reset every remembered Allow, a teammate opens Settings → General → Team Bots → Clear connector preferences.
Review learnings: the gate on team memory
Since v1.0.1, what teammates teach a Team Bot waits for sign-off instead of saving straight away.
Owners and Managers see Review learnings with a pending count under Suggested in the Bot's details. Each item states its effect, like Updates the skill or Forgets a team memory, with Approve and Reject.
The same queue sits under Manage → Knowledge → To review, and on the phone as Learnings.
Edits the owner or a Manager makes in the main chat skip the queue and apply right away.
📞 Rolling Team Bots out across a client team? Book a free SEO strategy session and my team will plan the sharing settings, roles and first workflows with you. → Get your free strategy session
Pushing a shared Bot into Slack and Microsoft Teams
Channel installs come after sharing and are done by the owner or a Manager.
Slack: Bot details or Manage → Channels → Bring to your team's Slack → Connect. Awaiting admin approval means a Slack workspace admin must approve the app.
Your access choice carries into Slack. Shared with the organization, any full workspace member can mention it. Shared with the team or chosen people, only they can. Guests and Slack Connect channels are always excluded.
Microsoft Teams: a team admin enables it, the owner or a Manager connects the Bot under Bring to your team's Microsoft Teams, and a Teams admin approves it. Full steps are on the Microsoft Teams page.
Error strings and what each one means
| Message | Cause | Fix |
|---|---|---|
| Team Bots Not Available | Account has no Team Bot access | Check the plan and team membership |
| Only team admins can share Bots | Bot sharing set to Admins only | Ask an admin to share it or change the setting |
| No Access to This Bot | Shared with certain people only | Ask the owner or a Manager to add you |
| Bot Not Found | Removed, or not shared with you | Confirm with the owner |
| This Bot's owner has reached their usage limit | Reply was billed to the owner | Owner checks their plan |
| Your admin has turned off sharing logins with Bots | Allow Shared Logins is off | Admin turns it on |
Templates: the other kind of sharing
If teammates or outside contacts should each get their own copy, share a template instead. The Bots docs path is Bot details → Share → Create a copy → Publish on the template card → Copy link. On mobile it's Share as Template.
New template links are public and expose identity, description, skills and routines. Scrub API keys, internal URLs and customer data before publishing.
Blocked? Your team doesn't allow public templates or Template sharing is turned off means an admin restricted Public template sharing.
Teardown: unshare, remove, delete
- Unshare everyone: Only you → Remove.
- Unshare one person: their role → Remove.
- Hide from your own sidebar: right-click → Remove from sidebar.
- Delete: owner right-clicks → Delete, or an admin deletes from Manage Bots. It's gone for the whole team with every chat and routine on it, permanently.
Prefer unsharing over deleting while you're still testing who needs the Bot.
Want the full playbook for Team Bots and agent workflows? The AI Profit Boardroom walks through it on video.
Also On Our Network
- 🌐 The owner-friendly way to give staff one shared AI helper
- 🌐 Every sharing option side by side, with who each one suits
- 🌐 The four sharing moves plus three Agent OS prompts to prepare the rollout
- 🌐 The sharing steps and admin switches, plus why the model does not matter here
- 🌐 The complete Grok Bot sharing guide on AI Profit Boardroom
FAQ: Grok Bot Sharing
Which plans let me share a Grok Bot as a Team Bot?
The Team and Enterprise plans, for members who have Grok Bot. Your team also needs at least one other member.
Does setting Bot sharing to Admins only unshare existing Bots?
No. Bots that were already shared stay shared, and their owners and Managers can still use them.
Can a Manager delete a Team Bot?
No. Only the owner can delete it from the sidebar, and a team admin can delete it from Manage Bots.
Why does my Bot say sharing logins is turned off?
A team admin has not turned on Allow Shared Logins, which is off by default. Until they do, Share your account is blocked.
Does a Team Bot use my apps or the owner's?
It uses the owner's apps for everyone. In your own chat it can also use yours, but it asks first with Allow once, Always allow or Skip.
What is the difference between a Team Bot link and a template link?
A Team Bot link opens the same Bot for everyone. A template link gives each person their own copy without your logins or history.
📺 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
Lock Bot sharing to Admins only, publish one tested Bot, check Review learnings weekly, and bring the setup to a free SEO strategy session or the AI Profit Boardroom if you want help running Grok Bot sharing across a team.











