Grok Bot sharing comes in more flavours than the single Share button suggests: you can share one live Team Bot with your team, your organization or named people, hand out a template copy, or share one app login through a shared connector, and each choice changes who sees what.

This guide walks through how to share, then lines the options up side by side so you pick the right one for each Bot.

Sources: the Team Bots docs, the Create and manage Bots page, the teams and enterprises guide and the changelog entry for v1.0.1.

The roles and admin dashboard are covered in our Grok Bot teams overview, so this page stays on sharing.

Weighing this up for your company? Book a free SEO strategy session and my team will help you choose the setup.

The five ways to share, at a glance

OptionWhat it doesWhat it needsBest for
Team Bot shared with your teamEveryone on the team chats with the same Bot, privatelyTeam or Enterprise plan, 2+ membersA job the whole team does
Team Bot shared with your organizationEveryone across the organization can use itA team inside an organizationHelpers several departments use
Team Bot shared with people you inviteOnly named people and groups get inConfirm with Limit accessBots touching client or finance data
Template copyEach person gets their own copy of the setupTemplate sharing allowed by your adminPartners, freelancers, other teams
Shared connectorEveryone uses one app through one accountAdmin turns on Allow Shared LoginsA low-risk tool everyone needs

The first three are the same mechanism with different reach. The last two solve different problems.

How to share a Team Bot, in order

  1. Choose + in the sidebar, then Create a Bot, and name it.
  2. Describe its job in a sentence.
  3. Add the apps, secrets, skills and files it needs. Until you publish, it's a draft only you can see.
  4. Choose Publish when the Bot says it's ready.
  5. Open Share at the top right of its chat and set Who has access.
  6. Add people under Add people or groups, set roles, and choose Copy link.

That's the whole flow. The decisions sit inside steps 3, 5 and 6.

Step 3 decides what the Bot can reach for every colleague. Step 5 decides how many colleagues that is. Step 6 decides who can change it afterwards.

Get those three right and the rest of sharing is housekeeping: approving learnings, adding channels, and occasionally removing someone who has moved on.

Decision 1: how wide to set access

Ask one question: does this Bot carry anything only some people should use?

If it does, pick People you invite. The docs ask you to confirm the change with Limit access.

If it doesn't, sharing with the team is fine.

Pick the organization only when other teams need it too. In Slack, a Bot shared with the organization can be mentioned by any full workspace member, even without a linked account, so organization-wide reach is genuinely wide.

Decision 2: who gets the Manager role

New people arrive as Collaborators, who can chat.

Managers can also change the Bot, share it, and approve what it learns for the team.

The owner and Managers can always use the Bot whatever the access setting.

Give Manager to the person who owns the process, not to everyone who asks. A Bot with six Managers has no clear owner.

๐Ÿ”ฅ Choosing between shared Bots and your own agent stack? 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 comparing what works. โ†’ Join the AI Profit Boardroom

Decision 3: Everyone or Admins only for Bot sharing

This is the admin's call, on the Grok Bot dashboard page under Sharing.

SettingWhat members seeSuits
Everyone (default)A working Share buttonSmall teams that trust each Bot's owner
Admins onlyShare disabled, with "Only team admins can share Bots"Teams that review Bots before rollout

Either way, Bots already shared stay shared. The changelog lists the setting as new in v1.0.1, described as letting team admins limit who shares Bots.

The admin guide's own recommendation is Admins only when Team Bots should be reviewed first, since each one carries its owner's apps, secrets and files into every teammate's chat.

Decision 4: individual logins or a shared connector

By default, each teammate's connected account is used only for that teammate.

A shared connector swaps that for one app. The owner or a Manager sets it under Setup then Service accounts, with three choices.

Connector choiceWho the Bot acts asTrade-off
Use individual accountsEach teammateMore setup, clearest accountability
Share your accountThe Manager who shared it, for everyoneFast, but every change runs under one person
The Bot's own accountA separate team accountNot supported by every app yet

Share your account stays locked until an admin enables Allow Shared Logins; it ships disabled.

Decision 5: share the Bot or share a template

Sharing a Team Bot points everyone at one live Bot, whereas a template hands each person a separate copy.

Choose the template when the other person should own and change their version freely, or sits outside your team.

Building one takes a few clicks from the Bot's details panel: Share, Create a copy, then Publish on the card it posts, followed by Copy link.

Recipients never receive your computer, logins or conversation history. They do see the Bot's identity, description, skills and routines, because a new template link is public.

Enterprise teams start with public template sharing off; other teams start with it allowed. If your admin has restricted it, publishing stops with a message saying public templates aren't allowed, or that template sharing is off.

What every teammate gets, whichever option you pick

  • A private chat that the owner and Managers can't open.
  • Approval prompts for risky actions, answered by the person who asked.
  • A prompt before the Bot uses their personal accounts.
  • Replies drawn from their own Grok Bot usage.
  • Team learnings that only land after the owner or a Manager approves them under Review learnings.

That last point arrived in v1.0.1 and it's the strongest safeguard sharing has. One teammate can't quietly rewrite the Bot for everyone.

Common mistakes when sharing a Grok Bot

  • Sharing a personal Bot as-is. Sharing doesn't duplicate it, so your personal files and keys go along. Use the phone's Copy or Start fresh option instead of Share when the Bot holds months of private context.
  • Organization reach by default. Wider than most Bots need, especially once it's in Slack.
  • Too many Managers. Every Manager can approve learnings and change apps.
  • Sharing a sensitive login. The docs warn to share only an account that holds nothing sensitive or private.
  • Deleting instead of unsharing. Deletion removes the Bot, teammates' chats and routines for good. Choosing Only you under access is reversible.
  • Forgetting the review queue. Learnings pile up unapproved and the Bot stops improving.

Where shared Bots can go after sharing

Once shared, the owner or a Manager can add the Bot to Slack from its details with Bring to your team's Slack, and a Slack workspace admin may need to approve.

Microsoft Teams follows a three-person chain: your team admin switches the integration on, an owner or Manager links the Bot, then a Microsoft Teams admin signs it off. The Microsoft Teams guide has the exact screens.

Admins can also push a Bot into members' sidebars with Auto-add under Manage Bots, which members can't hide.

๐Ÿ“ž Want a second opinion before you roll it out? Book a free SEO strategy session and my team will check your sharing settings, roles and first workflow with you. โ†’ Book your free session

A worked example: a five-person marketing agency

Picture an agency with an owner, two account managers, a designer and a copywriter.

They want one Bot that drafts monthly client reports from their analytics tool and project notes.

The owner builds it, adds a read-only analytics key and the report template, and runs three past months through the draft.

Access goes to People you invite: the two account managers only, because the designer and copywriter don't need client numbers.

One account manager becomes the Manager, so report tweaks don't wait for the owner.

The analytics tool stays on individual logins at first. Once everyone is comfortable, the owner can ask the admin to switch on Allow Shared Logins for that one low-risk account.

Every Friday the Manager clears Review learnings, approving formatting fixes and rejecting anything that looks client-specific.

The copywriter gets a template copy of a separate tone-of-voice Bot instead, so she can change hers without affecting anyone.

What sharing doesn't give you

  • No view into colleagues' chats. If you need oversight, that sits with Enterprise audit features, not with sharing.
  • No local Bots. Anything running on your own machine stays personal.
  • No model choice. Grok Bot manages model selection, and sharing doesn't change that.
  • No undo on delete. Unshare instead whenever you're unsure.

Who each setup suits

  • A team of under ten, one shared job: share with the team, one Manager, Bot sharing on Everyone.
  • A growing team with client data: People you invite, Bot sharing on Admins only, individual logins.
  • Several teams, one helper: share with the organization, auto-add for the groups that need it.
  • Agencies handing a setup to clients: a template copy, scrubbed of keys and internal links.
  • Everyone needs one low-risk tool: a shared connector, with Allow Shared Logins switched on deliberately.

Requirements to confirm first

Plans: Team or Enterprise. Headcount: two or more people on the team. Hosting: cloud only, since xAI rules out sharing any Bot that lives on a local machine.

Sharing from a phone needs Grok Bot 1.19.0 or later on iPhone or Android.

If Browse shared Bots is missing under +, you're either not on a Cursor team or the app needs updating.

Want to compare this with building shared agents yourself? The AI Profit Boardroom covers both sides on video.

Also On Our Network

FAQ: Grok Bot Sharing Options Compared

Which Grok Bot sharing option is the safest?

Sharing a Team Bot with People you invite, with individual logins and Bot sharing set to Admins only.

When should I use a template instead of a Team Bot?

When the other person should own a separate copy, or sits outside your team. Templates never include your logins or chat history.

Is a template link private?

A new template link is public, and it shows the Bot's identity, description, skills and routines. A team-only link opens only for your team.

Does sharing with the organization reach Slack users?

Yes. Any full member of your Slack workspace can mention a Bot shared with the organization, though guests and Slack Connect are excluded.

Can I undo sharing?

Yes. The owner chooses Only you under Who has access and confirms with Remove. Deleting the Bot is the step that cannot be undone.

What changed for sharing in v1.0.1?

Admins gained the Bot sharing limit, Managers gained shared connectors once Allow Shared Logins is on, and team learnings now wait for approval.

๐Ÿ“บ 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

Match the option to the Bot, not the other way round, and if you want help choosing, book a free SEO strategy session or learn the builds in the AI Profit Boardroom before you settle your Grok Bot sharing setup.