38 lines
2.4 KiB
Plaintext
38 lines
2.4 KiB
Plaintext
---
|
|
title: "Collections"
|
|
description: "Group plugins into reusable Cloud assignments for teams and members"
|
|
---
|
|
|
|
Collections are the advanced OpenWork Cloud tool for grouping multiple plugins and assigning them as one managed set. Use a Collection when the same team or members need several plugins, when you expect the set to change, or when individual plugin grants would become difficult to maintain.
|
|
|
|
For the simplest one-skill publishing flow, start with [Publish and copy a skill](/start-here/do-work-with-it/publish-and-copy-a-skill).
|
|
|
|
## How Collections work
|
|
|
|
- A plugin contains skills and can also contain other extension resources.
|
|
- A Collection contains one or more plugins.
|
|
- A Collection can be granted to everyone in the organization, selected teams, or individual members.
|
|
- The plugin creator keeps access automatically.
|
|
- Adding, updating, or removing a plugin changes the managed set for the Collection's audience. Members can use `Refresh` in `Settings > Library` if a recent change has not appeared yet.
|
|
|
|
## Create and assign a Collection
|
|
|
|
1. Open `Collections` in the OpenWork Cloud dashboard.
|
|
2. Click `New collection`, enter a clear name and optional description, then click `Create collection`.
|
|
3. Open `Plugin Directory` and create or edit each plugin that belongs in the Collection.
|
|
4. In each plugin's `Share` section, choose the Collection.
|
|
5. Return to the Collection and use `Who can access this` to add teams or individual members, or turn on access for everyone in the organization.
|
|
6. Ask a member to open `Settings > Library` in the desktop app and confirm the assigned plugins and skills are present.
|
|
|
|
Only owners and admins can create Collections and publish skills for other people by default.
|
|
|
|
## Keep complex setups manageable
|
|
|
|
- Create Collections around a stable audience or purpose, such as `Sales Enablement` or `Engineering Operations`.
|
|
- Put plugins used by the same audience in one Collection so one access change covers the whole set.
|
|
- Prefer team grants over many individual grants when membership changes often.
|
|
- Use separate Collections when audiences or update schedules differ.
|
|
- Review Collection access before adding a plugin that reaches sensitive systems.
|
|
|
|
For a complete organization walkthrough, see [Team quickstart](/cloud/team-quickstart). For managed service accounts and MCP servers, use [Connectors](/cloud/share-with-your-team/shared-mcp-connections) rather than placing credentials in a skill.
|