# Share a toolbox with your team

> Source: https://elaichi.ai/docs/guides/toolboxes/shared-toolboxes/

Build a reusable toolbox template, tune its tools, and share it so teammates can take their own copy under **My toolboxes**.

**Where to find it:** **Toolboxes → Shared toolboxes** (open a toolbox to edit it)

A shared toolbox is a **template**. Sharing it does not share your credentials. AI clients connect to personal copies under **Mine**, not to the template itself.

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

## Create a shared toolbox

1. Open **Toolboxes → Shared toolboxes** and create one. Name it after the job it does, such as “support triage”.
2. **Add tools** from connected products (and [synthetic tools](/guides/toolboxes/synthetic-tools) when you have them).
3. For each entry, decide whether to pin a connection or leave **No connection (user provides)** so each person binds their own.
4. 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 MCP 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 toolbox → **Share**.
2. Choose **A member**, **A team**, or **Entire organization**.
3. Set **Access level**:

| Level | Recipients can |
| --- | --- |
| **View** | See the toolbox and its tools |
| **Use** | Create a personal toolbox and run its tools (default) |
| **Edit** | Change tools and settings |

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

:::callout{type="info"}
If the toolbox relies on a **personal** connection, the share flow may nudge you to **Transfer to organization** so the connection outlives one person. Credentials stay in the vault; only ownership changes.
:::

## Instantiation (teammates)

Recipients with at least **Use**:

1. Open **Toolboxes → My toolboxes**.
2. Choose **New from template** (or the equivalent create-from-template action).
3. Pick this shared toolbox and create their copy.
4. Bind **Select a connection** for any tool that still shows **Needs connection**.

**You'll know it worked when:** Teammates see their copy under **My toolboxes** and can create an MCP server from it.

## Good to know

- A template alone can’t be used by an AI client — instantiate first (or use a connection/global toolbox under Mine).
- You only see templates you own or that were shared with you.
- Renaming a tool changes it only inside this toolbox.
- Restriction-blocked tools never reach MCP clients even if they’re listed on the template.

## Related

- [How toolboxes work](/guides/toolboxes/overview)
- [Your toolboxes](/guides/toolboxes/your-toolboxes)
- [Synthetic tools](/guides/toolboxes/synthetic-tools)
- [Create an MCP server](/guides/mcp-servers/creating-an-mcp-server)