# Share a template with your team

> Source: https://elaichi.ai/docs/guides/toolboxes/templates/

Build a reusable template, tune its tools, and share it so teammates can stamp their own toolbox from it.

**Where to find it:** **Toolboxes → Templates** (open a template to edit it)

A template is a tool list — names, descriptions, frozen params and defaults — with **no connections in it at all**. Sharing it never shares credentials, because there’s nothing to share: each person’s stamped toolbox picks its own connections.

You need `template:create` to build one and `template:share` to share it.

## Create a template

1. Open **Toolboxes → Templates** and create one. Name it after the job it does, such as “support triage”.
2. **Add tools** from any connector (and [synthetic tools](/guides/toolboxes/synthetic-tools) when you have them) — no connection required.
3. Tune each tool with **Edit tool**:

| Control | Use it to |
| --- | --- |
| **Name / description override** | Speak in your team’s language so agents pick the right tool |
| **Enabled** | Hide a tool from a stamped toolbox without deleting it |
| **Frozen parameters** | Lock a project, pipeline, or workspace the model must not change |
| **Default values** | Suggest values the model may override |
| **Input schema override** | Narrow or reshape what the client advertises |

Precedence at call time: defaults < client args < frozen params.

## Share it

1. Open the template → **Share**.
2. Choose **A member**, **A team**, or **Everyone** (everyone at your organization).
3. Set **Access level**:

| Level | Recipients can |
| --- | --- |
| **View** | See the template and its tools |
| **Use** | Stamp their own toolbox from it and run its tools (default) |
| **Edit** | Change tools and settings |

4. Add the share. Badges show **Can view** / **Can use** / **Can edit**.

## Stamping (teammates)

Recipients with at least **Use**:

1. Open **Toolboxes** → **New toolbox**.
2. Pick this template.
3. Name the new toolbox. For each connector the template’s entries need,
   choose one of your connections — or skip it and fill it in later.
4. Create it. Entries land **Ready** where you picked a connection, or
   **Needs connection** where you skipped one.

**You'll know it worked when:** the new toolbox appears under **Toolboxes**, and its `Ready` entries already run.

:::callout{type="info"}
Stamping copies the template’s entries once. Editing the template afterward
never changes toolboxes already stamped from it — `template_id` is kept only
as provenance, so you can see where a toolbox came from.
:::

## Good to know

- A template alone can’t be used by an AI client — stamp a toolbox first (or use a connection/global toolbox, which need no template at all).
- You only see templates you own or that were shared with you.
- Renaming a tool changes it only inside this template — the underlying product is untouched, and toolboxes already stamped from it keep whatever name they copied.
- Restriction-blocked tools never reach MCP clients even if they’re listed on the template.

## Related

- [How toolboxes work](/guides/toolboxes/overview)
- [Toolboxes](/guides/toolboxes/toolboxes)
- [Synthetic tools](/guides/toolboxes/synthetic-tools)