agentos.guide › blog
Grok Bot sharing turns one of your Bots into a Team Bot that colleagues open from a link, each in a private chat, and the setup takes four moves: create, publish, share, set access.
Below are those moves in order, the settings that decide who may share, and three Agent OS prompts that do the preparation for you: auditing the Bot before it goes out, writing the rollout note, and running the weekly learnings review.
Facts come from xAI's Team Bots docs, the teams and enterprises guide and the v1.0.1 changelog.
New to Team Bots? Start with the Grok Bot teams overview for roles and the dashboard.
Planning a rollout for a client or your own organisation? Book a free SEO strategy session and we will map it with you.
Check by choosing + in the sidebar. If Browse shared Bots shows, you're ready.
You can share a Bot you already use instead. It isn't duplicated, so tidy its setup first. Prompt 1 below does that audit.
Press Share, top right of the chat. In Share this Bot:
| Choice | Result |
|---|---|
| Your team | Everyone on the team can chat with it |
| Your organisation | Everyone in the organisation can chat with it |
| People you invite | Only people and groups you add; confirm with Limit access |
| Manager role | That person can also change and share the Bot |
| Copy link | A link that opens the same Bot for everyone |
| Only you | Stops sharing after you confirm Remove |
Added people start as Collaborators. The owner and Managers can always use the Bot.
🔥 Run your own shared agents too
Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video trainings, four coaching calls a week and 3,400+ members.
Team admins pick Everyone (the default) or Admins only under Sharing on the Grok Bot dashboard page.
With Admins only, members find Share greyed out with Only team admins can share Bots. Already-shared Bots stay shared.
The changelog added this in v1.0.1 on 11 November 2026. xAI's guide suggests Admins only when Bots should be reviewed before colleagues use them.
An owner or Manager opens the Bot's details, then Setup, Service accounts, and picks an app under Shared connectors.
Choosing Share your account makes everyone act through that login, edits included. It's blocked until a team admin enables Allow Shared Logins, which starts off.
Reserve it for accounts with nothing sensitive in them.
Paste this into your Agent OS with the Bot's setup notes or a screenshot description of its Plugins, Secrets, Skills and Files panels.
You are reviewing a Grok Bot before I share it as a Team Bot.
Everything listed below will work in every teammate's chat.
For each app, secret, skill and file:
1. Say whether a new starter on my team should have it.
2. Flag anything personal, client-specific or admin-level.
3. Suggest a narrower replacement where one exists.
Then give me a short keep / remove / replace list and one line
saying whether to share with the team or only with invited people.
Setup:
[paste the Bot's apps, secrets, skills and files here]
Remove whatever it flags, then publish.
Write a short message to my team announcing a shared Grok Bot.
Bot name: [name]. Its job: [one sentence].
Include: how to open it (the link, or + then Browse shared Bots),
that each person's chat is private, that it asks before using
their own accounts, that team learnings are reviewed weekly by
[Manager name], and two example requests they can try today.
Keep it under 150 words, friendly and direct, UK spelling.
Send it with the link from Copy link.
Below are the pending items from my Team Bot's Review learnings
queue. For each one, tell me Approve or Reject and why, in one line.
Approve only changes I would teach a new hire.
Reject anything personal to one colleague, anything that widens
what the Bot can send or change, and anything vague.
Pending items:
[paste each suggestion, e.g. "Updates the skill: ..."]
Then press Approve or Reject on each item in the Bot's details.
📞 Want this mapped for your team?
Book a free SEO strategy session and my team will plan the Bot, the access level and the review routine with you.
Per the Bots page, choose Share then Create a copy in the Bot's details, publish the template and copy the link.
A new template link is public and shows the Bot's identity, description, skills and routines. Each recipient gets a copy without your computer, logins or history.
Teams can restrict this with Public template sharing, which starts off on Enterprise.
Run through these five points before anyone else sees the Bot.
If any point fails, fix it in the draft. Nobody can see a draft but you, so there's no cost to taking your time.
Channels come after the share, and only the owner or a Manager can add them.
For Slack, open the Bot's details, find Bring to your team's Slack and choose Connect. If it shows Awaiting admin approval, your Slack workspace admin has to approve the app.
The access level you picked follows the Bot into Slack. Organisation-wide sharing lets any full workspace member mention it; narrower sharing keeps it to the people you chose. Slack guests and Slack Connect channels never get in.
For Microsoft Teams, your team admin enables the integration, the owner or a Manager connects the Bot, and a Microsoft Teams admin approves it, as the Microsoft Teams page lays out.
To pull access from everyone, the owner chooses Only you and confirms with Remove.
To drop a single colleague, open their role in the list and choose Remove.
Deleting is different: only the owner, or an admin from Manage Bots, can do it, and it wipes the Bot for the whole team along with colleagues' chats and routines. There's no way back, so unshare first while you decide.
Learn the full Agent OS workflow for prompts like these inside the AI Profit Boardroom.
Four: create the Bot, publish it, press Share, and set who has access. Sending the link is optional.
The prompts here prepare the audit, the rollout note and the learnings review. You still press Share and Publish in the Grok Bot app.
No. A Team Bot link opens the same Bot for everyone, each in a private chat. Only a template gives people their own copy.
The owner or a Manager, under Review learnings in the Bot's details, with Approve and Reject on each suggestion.
Your admin set Bot sharing to Admins only. Ask an admin to share it for you.
A Bot that runs on your own computer, and any Bot on a team where you are still the only member.
Audit, publish, share narrowly, then review learnings every week; for help, book a free SEO strategy session or install the Agent OS from the AI Profit Boardroom and let it prepare your Grok Bot sharing rollout.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Grok Bot Teams: Plan, Audit And Roll Out A Shared Bot With 5 Prompts In Your Agent OS
→ Grok Bot Connectors: Connect, Track And Reconnect Every App In Your Agent OS
→ Grok Bot Microsoft Teams: Plan The Rollout In Your Agent OS
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉