---
title: "Share A Gobii Template"
description: "Prepare a Gobii for public sharing as a reusable template and keep sensitive access out of the shared artifact."
sidebar_label: "Share A Template"
---

Sharing a Gobii template lets other people create their own Gobii from a role you have designed. Share templates only after removing private context and confirming the behavior is safe for a new workspace.

## What a template can include

A public template can describe:

- Name and display information.
- Tagline and description.
- Category.
- Charter or standing instructions.
- Suggested tools or app expectations.
- Schedule or event-trigger guidance.
- Public profile attribution.
- Optional imagery or library metadata where supported.

The created Gobii can then be customized by the person who starts from the template.

## What not to include

Do not put private or sensitive material in a shared template:

- Credentials, passwords, API keys, tokens, cookies, or private URLs.
- Customer names, emails, phone numbers, or private contact lists.
- Internal business data.
- Proprietary prompts that should not be public.
- Instructions that assume access to your private files or apps.

Use placeholders instead:

> Connect your CRM and provide a target account list before running outreach research.

## Prepare a Gobii for sharing

1. Review the charter for sensitive details.
2. Remove or generalize private examples.
3. Make setup requirements explicit.
4. Confirm the Gobii asks before external communication.
5. Remove workspace-specific files and credentials.
6. Test the template by creating a new Gobii from it when feasible.
7. Publish through the sharing controls available in your workspace.

## Write useful template descriptions

A strong template page tells a future user:

- Who the Gobii is for.
- What result it helps produce.
- What inputs it needs.
- What tools or apps may be useful.
- What approval boundaries are recommended.
- Whether the work is one-time or ongoing.

## After sharing

Review template feedback and update the template if users misunderstand the role, connect the wrong tools, or need clearer setup instructions. Treat templates as living product artifacts, not static prompt snippets.
