> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# Collections

> Group several plugins for the same audience in OpenWork Cloud, so one access change covers the whole set.

A Collection groups several plugins so you can give them to the same people in one step. Anyone with access to the Collection gets every plugin in it, in the desktop app.

Collections are optional. The simplest way to share a skill or plugin is to set **Who can use it** on its own page. See [Publish and copy a skill](https://openworklabs.com/docs/start-here/do-work-with-it/publish-and-copy-a-skill.md).

Only owners and admins can create and manage Collections.

## When to use a Collection

| Use direct sharing when... | Use a Collection when... |
| - | - |
| You're sharing one skill or plugin. | The same team needs several plugins. |
| Each plugin goes to different people. | You want one place to change who gets the whole set. |
| A member is sharing something they made. | You expect to add plugins to the set over time. |

You can use both. A person gets a plugin if any route gives it to them: direct sharing, a Collection, or everyone in the organization.

## Where to find Collections

In the OpenWork Cloud dashboard, open **Settings › Advanced** and select the **Collections** tab.

The built-in OpenWork collection and any Collection assigned to you show up in the desktop app after sign-in.

## Create a Collection

1. Open **Settings › Advanced › Collections** and click **New collection**.
2. Enter a **Name**, like `Sales Enablement`, and an optional description.
3. Click **Create collection**. The new Collection opens.

To rename or delete a Collection later, use its ⋯ menu and choose **Edit** or **Delete**. The built-in collection can't be deleted.

## Add plugins

1. Open the Collection. On the **Plugins** tab, click **Add a plugin**.
2. Enter a **Plugin name** and **Description**.
3. Under **What's inside**, add a **Skill**, **Command**, or **Connector**. To bring in an existing plugin from a GitHub repository, click **Import from GitHub** instead.
4. Under **Share**, check that **Collection** shows this Collection.
5. Leave **Share with everyone in the organization** off if only the Collection's audience should get the plugin.
6. Click **Create plugin**.

Plugins can also arrive automatically from a connected source repository. Before you have any Collections, the Collections tab shows **Open Sources** so you can connect one.

> [!NOTE]
>
> The dashboard puts a plugin in a Collection when you create it from that Collection. To share a plugin that already exists, set **Who can use it** on the plugin's page instead.

If a plugin needs a connector, the **Configure** tab lists each one and whether it's ready. A plugin may show **Members need sign-in** or **Needs connection** until that's done. For connector setup, see [Sharing MCP connections](https://openworklabs.com/docs/cloud/share-with-your-team/shared-mcp-connections.md).

## Choose who can access it

1. Open the Collection and select the **Members** tab.
2. Under **Who can access this**, do one of the following:
   * Turn on **Everyone in** followed by your organization's name.
   * Click **Add team** and pick one or more teams.
   * Click **Add people** and pick individual members.

Changes apply to every plugin in the Collection. Anyone added to a team later gets the team's Collections automatically.

## See what a team can use

To check what a team has, and why:

1. Open **Members**, select the **Teams** tab, and click the team.
2. Select the **Access** tab and scroll to **Plugins & connections**.

Each plugin shows how the team got it:

* **direct team grant**: the plugin was shared with this team directly. Click **Revoke** to remove it.
* **via catalog:** followed by a Collection name: the team gets it through that Collection. Click **Open catalog** to change the Collection's access.
* **org-wide**: the plugin is shared with everyone in the organization.

## Where members find the plugins

Members open **Settings › Library** in the desktop app. Plugins and skills from their Collections appear under **From OpenWork**. If a recent change hasn't appeared yet, they can click the refresh button (its tooltip says **Refresh**).

## Keep larger setups manageable

* Build each Collection around a stable audience or purpose, such as `Sales Enablement` or `Engineering Operations`.
* Grant Collections to teams rather than many individual people when membership changes often.
* Use separate Collections when audiences or update schedules differ.
* Review a Collection's access before adding a plugin that reaches sensitive systems.
* Put service accounts and credentials in [connectors](https://openworklabs.com/docs/cloud/share-with-your-team/shared-mcp-connections.md), never in a skill.

## Related

* [Share skills and MCP servers with your team](https://openworklabs.com/docs/start-here/do-work-with-it/share-your-setup.md)
* [Publish and copy a skill](https://openworklabs.com/docs/start-here/do-work-with-it/publish-and-copy-a-skill.md)
* [Team quickstart](https://openworklabs.com/docs/cloud/team-quickstart.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.