How to share a Grok Bot: template links, the Marketplace, and Team Bots (unofficial guide)

Two ways to share a Bot: a template or a Team Bot

A template is a copy. Per the official docs, "Adding a shared Bot creates a copy on the recipient's account. It does not give them your computer, logins, or conversation history." xAI's own templates guide calls it "a recipe, not a clone": the other person cooks their own version, and from then on each copy is maintained separately by its new owner.

A Team Bot is one shared Bot. The docs define it as "one Bot that your whole team talks to." The owner sets it up once with plugins, secrets, skills, and files, publishes it, and every teammate chats with it in the Grok Bot app or in Slack. Each person's chat stays private, and changes the owner makes reach everyone.

Rule of thumb: share a template when you want people to start from your setup and make it their own. Publish a Team Bot when you want one teammate that everybody uses and you keep improving. @grok summed it up in an Oct 14, 2026 reply: "Templates only make independent copies."

Duplicate is a third, private option. Duplicating a Bot inside your own account copies its profile, settings, enabled skills, routines, and avatar, but not its conversation history, learned memory, or chat attachments (docs). Use it for a second version of your own Bot, such as one per region.

What a template link shares, and what it doesn't

What goes with it: a public link "shows the Bot's shared configuration, including its identity, description, skills, and routines" (docs). xAI's templates guide adds that a template copies "the bot's instructions, relevant memories and skills, and specific plugins," and that the Bot "left out personal or internal memories" by default. Choose View template details to see exactly what was packaged.

What doesn't go with it: your computer, your logins, and your conversation history (docs). The templates guide says custom code and scripts aren't included, and that "non-standard plugins like MCP servers or other scripts or code" have to be set up again by the new owner. Plugins that are included still need the recipient to connect their own accounts.

Secrets: xAI's guide says "Templates do not include secrets." But any text written into the Bot's description, skills, memories, or routine instructions does travel. That's why the docs say: "Remove API keys, internal URLs, customer data, and anything else you would not put in a public document before you share." The third-party bot terms put it bluntly: "Anyone with the share link can view and install your bot's full configuration, including skills, routines, and identity content."

Updates: after you share, the Share menu offers Update template. Per the docs' comparison table, each copy is maintained by its new owner separately, so don't count on later edits reaching copies people already added. The docs don't describe how to take a template down once it's shared. Assume a public link stays usable by anyone who has it.

How to share a Bot as a template link

From the official docs: open the Bot's Share menu and choose Create template. The Bot builds the template, and then Copy link, View template details, and Update template appear. Older walkthroughs, including xAI's Sep 8 guide, call the button Share as Template. You can also just ask. xAI's Lingxi Li on X (Oct 3, 2026): "you can export them into a bot template (just ask your bot to export)."

Choose who can open it: Public link or Team-only. A public link opens for anyone who has it. A Team-only link opens only for members of your team. Enterprise accounts default to Team-only, other accounts default to a public link (docs). On Teams and Enterprise, admins can turn public template sharing off, and Cursor then enforces team-only sharing on its servers, "including for templates that are already public."

Then send the link. The recipient sees a preview on x.ai and chooses Add to Grok Bot.

A known bug: some personal-plan users report that sharing fails with "A team must be selected to share a team template." A Cursor staff member said on the Cursor forum that it's caused by old, empty team memberships still attached to the account on the back end, and that it's being tracked. As of Oct 15, 2026, users in that thread were still reporting it. If you hit it, contact Cursor support and reference that error.

How to add someone else's template (and vet it first)

Open the template link. You'll see its preview on x.ai. Choose Add to Grok Bot. You need the Grok Bot app installed, which is separate from the regular Grok chat app (per an @grok reply on X). In the app you can review the context and integrations included before you choose Add Bot (xAI templates guide).

Where to find them: the x.ai Marketplace (x.ai/bot/marketplace) lists templates by category, including a From Grok Bot Team section with Bots like Outbound Prospecting, Recruiting Coordinator, Haggle Bot, and Office Ops Desk. Per the Oct 2 changelog, the in-app Marketplace became Connect Apps (for plugins), with Bot templates on the web. Per the Oct 11 changelog, you can also describe what you need and your Bot "can find a Bot template that fits" and link it in chat. Many more are shared as plain links on X.

Read it before you add it. Every third-party share page carries a notice: "This AI bot was created by a third-party user, not by SpaceXSI. It may act on your behalf." Adding one accepts the third-party bot terms, which say the bot may read, write, and send data through your connected accounts, that SpaceXSI "does not verify, endorse, or guarantee the functionality or safety of third-party bots," and that you may not "redistribute, re-share, or re-export this bot or its configuration without the creator's permission." xAI's own advice: "Evaluate templates just like you would evaluate skills or software."

Our vetting checklist (our suggestion, not official): 1) Read the description and every skill and routine. 2) Look for instructions to install code from GitHub, run scripts, or contact people. 3) Check which plugins it wants and connect only the ones its job needs. 4) Run it once while you watch, with drafts only. All your Bots share one computer and its logins, so a new Bot isn't a security boundary (official FAQ).

Team Bots: who can use them and how they work

Who can use them: Cursor's help center says Team Bots "are for members of a Cursor team who have Grok Bot." A Sep 29, 2026 reply from @grok said they're "in public beta for Cursor Teams and Enterprise" and that "Individual Cursor Pro plans include Grok Bot but not Team Bots." Per the official FAQ, self-serve Cursor Teams Standard and Premium seats include Grok Bot. If you don't see Create new Team Bot under New chat, Team Bots aren't on for your team yet.

Some solo users wish they could share a Bot more widely. One SuperGrok subscriber wrote on X that he'd like to share a finance Bot with his spouse, "Not just a template but a bot with memory of each user," and that he'd "just found out" his plan "does not have the team bot functionality." For a solo plan today, a template is the sharing option.

How to create one (docs): choose New chat (or Cmd/Ctrl+N), then Create new Team Bot. The Bot asks what the team needs and walks you through plugins, secrets, skills, and files. To turn an existing Bot into one, open its Share menu and choose Publish to Team. You pick which plugins, secrets, memories, skills, files, and routines the team copy gets, and your personal Bot stays private. Choose Publish to team when it's ready. Teammates find it under New chat, then Team Bots, or through a link you copy.

How it behaves: each teammate's chat is private, and the owner can't read it. When someone says the whole team should know a fact, the Bot saves it to team memory. A plugin that signs in with an account uses the account of whoever is asking, so "A Team Bot never lends one person's access to another." Usage counts against each teammate's own allowance, not the owner's. Routines are personal and run only for whoever set them up. Owners can add managers who can change the setup, and a published Team Bot can get its own Slack app (docs).

Secrets on a Team Bot are handled properly: values are encrypted, teammates never see them, and the Bot itself uses them by name, with values shown as [REDACTED] in its output. Up to 25 per Team Bot. The docs' advice: "treat a secret as access you are giving the whole team" and use "scoped, read-only service-account keys instead of personal credentials."

Approvals: Cursor's help center says a Team Bot asks for approval only in its owner's own chat. In teammates' chats, in Slack, and in group chats, "the Bot works within the permissions its owner set up, without stopping to ask," unless an Enterprise admin enforces Auto-review. (xAI's Oct 11 changelog also says teammates can approve Auto-review requests from their own direct message with a Team Bot, so check how yours behaves.) The safe design either way: only give a Team Bot permissions you'd be comfortable with it using unasked.

How to scrub a Bot before you share it

Start with View template details and read every line, the way a stranger would.

Remove what the docs and terms name: API keys, internal URLs, customer data, and personal information. Check the description, each skill, each routine's instruction, and any memories the template includes.

Replace specifics with placeholders (our suggestion): [YOUR COMPANY], [YOUR CRM], [YOUR API KEY]. Then write the setup steps into the description so the new owner knows what to connect. xAI's guide recommends this for complex templates: "you can tell the bot to encode instructions for setup."

If a real key was ever in a skill or description you shared, rotate it in the service it belongs to (our suggestion, standard security practice). For keys a Team Bot needs, use its Secrets card rather than pasting them anywhere. The docs' member advice: "Never paste credentials into chat."

Use Team-only for anything company-specific. xAI's guide shows the author choosing Team for a Bot "very specific to coding at SpaceX" for exactly that reason.

How founders can use templates and Team Bots

These are our suggestions, not official recommendations.

1. An onboarding Team Bot. Upload your handbook, FAQs, and process docs as Team Bot files (.txt, .md, .csv, .json, .yaml up to 256,000 characters each, per the docs), add your how-tos as team skills, and let new hires ask it anything in private. Each person's usage comes from their own allowance.

2. Standardize a role with a Team-only template. When your best inbox or follow-up Bot finally works, share it Team-only so each person starts from the same setup and connects their own accounts.

3. Start from xAI's own playbooks. The Marketplace's From Grok Bot Team section includes Outbound Prospecting, Recruiting Coordinator, and Office Ops Desk. xAI's Team Bots launch post describes how it uses Team Bots internally for account briefings, engineering, marketing review, and data questions, and quotes a customer, Harper's CEO: "We built a Team Bot in 24 hours to automate this, saving our customers over $120,000 from hundreds of policies." That's their reported result.

4. A free template as a lead magnet. Give away a Bot that does one useful job, with your business named in the description. One local SEO consultant on X posts real audit results alongside a free template link: "The same audit my Grok bot runs for free," adding that it "reads up to 500 pages, changes nothing, and writes the report in plain words." Another creator labels his templates "Unofficial, not affiliated with SpaceXAI. Grok Bot template by SMF Works." The third-party terms make you responsible for "Applying all appropriate disclosures," so say who made it and what it does.

5. Getting paid: we found no documented way to charge for a template inside Grok Bot. X runs an invite-only Grok Bot Template Rewards Pilot (terms effective Sep 25, 2026, expected to last about two months) that may make discretionary payments for public templates posted on X. The terms say "This is not a revenue share," require US residence, an eligible X Premium tier, and X Money, and require X's paid partnership label on promotional posts. Sawyer Merritt said he earned $500 in two weeks from his Home Robots template; that's his reported result.

This is moving fast. Templates arrived Aug 28 and Team Bots in late September, so a Bot you package this month could be a head start for your whole team. This guide is independent and unofficial. It isn't affiliated with or endorsed by xAI, Grok, or Cursor.