Share a bot as a template

Member·4 minutes to read

What this does for you

Sharing a bot as a template turns its instructions, skills, routines and a copy of its private memory into a catalogue entry that a teammate — or, if your organisation allows it, anyone with the link — can use to create their own bot with the same job.

Before you start

  • You are signed in and the bot appears in your sidebar (using/start-here).
  • You are the bot's owner. Anyone who can see a team-visibility bot can start a share, but only the owner can publish, download or withdraw it.
  • If you want a Public template, your organisation is a team organisation, not a personal one, and an administrator has not turned Template sharing to Off or Team-only (Settings → Policies).

Steps

  1. Open the bot's context menu in the sidebar and choose Share as template, or open the bot's settings panel and select Share as template at the bottom of the panel.

    <!-- shot: share-a-bot-01-phone.png | Choosing Share as template from a bot's context menu, on a phone --> <!-- shot: share-a-bot-01-desktop.png | Choosing Share as template from a bot's context menu, on a desktop -->
  2. Read the bot's own message describing what it found — its skills, its routines and its installed plugins — then select View Details on the template card underneath it.

    <!-- shot: share-a-bot-02-phone.png | The template card in the conversation, on a phone --> <!-- shot: share-a-bot-02-desktop.png | The template card in the conversation, on a desktop -->
  3. In the sheet that opens, choose who can use the template — Team or Public — and whether to publish it under your organisation's name or your own. Then read the scan verdict at the bottom of the same sheet.

    <!-- shot: share-a-bot-03-phone.png | Choosing an audience and reading the scan verdict, on a phone --> <!-- shot: share-a-bot-03-desktop.png | Choosing an audience and reading the scan verdict, on a desktop -->
  4. Untick any memory, skill or routine that should not leave the organisation, then select Publish. Select Download instead if you want the same pack saved as a file rather than added to the catalogue.

    <!-- shot: share-a-bot-04-phone.png | Unticking a memory before publishing, on a phone --> <!-- shot: share-a-bot-04-desktop.png | Unticking a memory before publishing, on a desktop -->

A worked example

You can start the same turn yourself instead of using the menu — send the bot this exact message and it opens the same card:

Create a template of yourself that I can share with somebody else.

What can go wrong

What you seeWhyWhat to do
Only the bot's owner can do this.Template actions check the bot's ownership before any write. A team member can open the sheet and read it, but only the owner can publish, download or withdraw.Ask the bot's owner to share it, or duplicate the bot without its memory and share your own copy.
1 finding must be removed before publishing.The scan found a secret or a credentialed address in the bot's instructions, a skill, a routine, or a memory you left ticked.Untick or edit the row the scan named. The scan reruns and the count drops.
Template sharing is off for this organisation.An administrator turned the organisation's Template sharing setting to Off.Ask an administrator to change it on the Policies page, or use Download to keep the pack outside the catalogue.
Public sharing is off for this organisation.The organisation's Template sharing setting is Team, so only a Team audience is available.Publish to Team, or ask an administrator to switch the setting to Public.
Public sharing is available to team organisations.Your organisation is a personal organisation, which has no Policies page and so no Public setting.Publish to Team, or create a team organisation first.
This proposal came from a task that read outside content. Ask the bot again in a fresh conversation.The share request was flagged as tainted, so the sheet cannot be trusted to publish, download or accept ticks.Start a new conversation and ask the bot to create the template again.

See also

Last verified against build 9e6bdf2.