How to share a Grok Bot template
xAI three steps: copy the share link, send it, the recipient previews on x.ai and adds a copy. What the public link shows and what to strip out first.
Sharing a Grok Bot template takes three steps, and xAI’s Bots documentation gives them in order: open the bot and copy its share link, send the link, and the recipient opens a preview on x.ai and chooses Add to Grok Bot. They need the Grok Bot app to finish adding it. The link is public and shows the bot’s identity, description, skills and routines to anyone who has it.
This page sticks to what the docs say. Where the docs are silent, it says so rather than guessing at a menu.
What are the exact steps?
Quoting the docs’ sharing section in full:
- “Open the Bot and copy its share link.”
- “Send the link. The recipient opens a preview on x.ai and can choose Add to Grok Bot.”
- “They need the Grok Bot app to finish adding it.”
The FAQ says the same thing in one sentence: “Anyone with the link can preview it on x.ai and add a copy to their account.” The feature went live on 28 August 2026 (announcement).
The docs do not say which menu holds the share link, and this page will not invent one. Open the bot’s profile and look for the share action there.
What does the recipient get?
A copy on their own account. The docs say adding a shared bot “creates a copy on the recipient’s account” and does not transfer your logins or conversation history. What the copy carries is the same set the docs list for a duplicated bot: “the profile, settings, enabled skills, routines, and avatar.” What it leaves behind: “conversation history, learned memory, or chat attachments.”
| Question | What the docs say | Source |
|---|---|---|
| Who can open the link? | Anyone who has it. "The link is public." | Bots |
| What does the link show? | "Identity, description, skills, and routines" | Bots |
| Does it share my computer or logins? | No. "It does not share your computer or logins." | Security |
| Does the copy carry memory? | No. Not conversation history, learned memory or chat attachments. | Bots |
| Can the link be revoked? | Not stated. | None found |
| Does the link expire? | Not stated. | None found |
Scroll sideways for the source column on a narrow screen.
What should I remove before I share?
The docs are direct: “Remove API keys, internal URLs, customer data, and anything else you would not put in a public document before you share.” The security page repeats it: “do not put secrets, customer data, or internal URLs in a Bot you share.”
That instruction is easy to follow if the bot was built for sharing from the start, and hard if it was not. A bot that has been running for a month tends to accumulate a customer name in a routine, a sheet URL in the instructions, a Slack channel id in a skill. Every one of those is visible in the public preview.
The way a template avoids this is placeholders. Every Botemplate paste block uses named placeholders for the owner, the time zone, the register sheet and every threshold, so the shared configuration contains nothing that belongs to any one company. The buyer fills them in on their own copy, in their own account. Quartermaster, for example, never holds a vendor name or a contract value in the template; those live in the buyer’s register sheet, which the docs’ rules would forbid in a shared bot anyway.
What does a share link not solve?
A share link moves configuration and nothing else, so everything a working bot needs beyond configuration still has to be done by the person receiving it. Four things. Connectors: xAI’s computer page says installed connectors are account-wide, and a shared bot “does not share your computer or logins,” so the recipient authorises Stripe, QuickBooks or Slack on their own account. Placeholders: a template written for sharing carries them, and a placeholder left in place gets quoted back verbatim by the bot. Approval rules: the docs describe Require Approval and Always Allow rules as something the account holder writes, and nothing in the sharing section says they travel with the bot, so check them after adding rather than assume. Verification: nothing in the sharing flow tests the copy. A template without acceptance tests hands the recipient a bot they cannot prove works. Every Botemplate bot ships a SETUP.md for the first three and an EVAL.md for the fourth; how it works describes the hour they take.
Is there a difference between sharing and duplicating?
Yes, though the copy is the same. Duplicating makes a second bot on your own account, named “<name> copy”; the docs suggest it for “the same role as a starting point for a different scope, for example one Account Health Bot per region.” Sharing publishes a link so someone else can add the copy to their account. Both leave memory and history behind.
For a template seller the practical difference is who owns the computer the copy runs on. A duplicate shares your account’s files, sessions and connectors. A shared copy runs on the recipient’s computer with none of yours, which is the whole reason a template must carry its setup order in a document rather than assume anything is already authorised.
How does Botemplate deliver a shared bot?
Through Polar, the merchant of record. A buyer pays on Polar’s hosted checkout, lands on Polar’s confirmation page, and gets Polar’s receipt email about a minute later with the download: a ZIP of the bot’s documents and a LINK.txt holding the share link. Opening that link is step 2 of the docs’ flow, and adding the copy is step 3. There is no call and nothing sent by hand. The five bots together are the Operator Pack at $69, one ZIP with five folders and five links.