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

# Creating and sharing a Collection

> How to build a Collection of apps and share it with individuals, groups, or organizations.

This page covers the create and share flow. For the concept, see [Share with Collections](/features/collections/What%20are%20Collections).

## How to create a Collection

<Steps>
  <Step title="Go to your organization">
    Open the org dashboard. Collections are an org-level container.
  </Step>

  <Step title="Open the Collections tab">
    The tab lists existing Collections in your org and shows a button to create a new one.
  </Step>

  <Step title="Click New Collection">
    The Create Collection form opens.
  </Step>

  <Step title="Name and describe">
    Pick a clear name. The description is for recipients to understand what the Collection contains.
  </Step>

  <Step title="Add apps">
    Click **Add Apps**. Search for apps you have access to and pick the ones to include. You can change the contents anytime.
  </Step>

  <Step title="Save">
    The Collection is created. You land on its overview page where you can manage apps and share.
  </Step>
</Steps>

<Info>
  The **New Collection** button appears only if you have permission to create Collections in your organization. If you don't see it, check with an org admin about your role.
</Info>

## How to share a Collection

<Steps>
  <Step title="Open the Collection">
    Go to the Collection's overview page.
  </Step>

  <Step title="Click Share">
    The **Share** button is in the top right.
  </Step>

  <Step title="Type the recipient">
    Add an individual, a group inside your org, or another organization. The recipient picker is the same as for app sharing.
  </Step>

  <Step title="Set permissions">
    Pick the permission level. For most cases, **Viewer** is the right level.
  </Step>

  <Step title="Send">
    The Collection appears in the recipient's view. They can add it to workspaces or use the apps directly.
  </Step>
</Steps>

## Updating a Collection

A Collection's contents aren't fixed. From the Collection's page, click **Add apps** to add more, or use an app card's **⋯** menu to **Remove from collection** — in both your org's **Collections** tab and your personal **My Collections** view. Removing an app takes it out of the Collection without deleting it. For the full walkthrough, see [Managing apps in a Collection](/features/collections/Managing%20Apps%20in%20a%20Collection).

Recipients see the updated set on their next visit. They do not need to re-add the Collection. Apps you remove disappear from recipient views; apps you add appear automatically.

When the owner of an app inside the Collection publishes a new version, recipients see the new version too. Updates flow through the Collection.

## Permission levels for Collections

**Viewer** (most common)

Recipients can use the apps in the Collection. They cannot edit the Collection itself or the apps inside.

**Editor** (rare)

Recipients can add or remove apps from the Collection. Useful for co-curation between orgs. Requires that the editor has access to the apps they want to add.

For most partner deployments, Viewer is the right level. Editor is for collaborative curation between trusted partners.

## Key points

<Info>
  * Create from your org dashboard, name it, and add apps
  * Share via the same Share modal as apps (individuals, groups, orgs)
  * Default permission is Viewer; Editor is for collaborative curation
</Info>

## FAQ

<AccordionGroup>
  <Accordion title="Does removing an app from a Collection delete it?">
    No. **Remove from collection** only takes the app out of that Collection. The app stays in its original workspace, keeps its owner, and remains in any other Collections it belongs to.
  </Accordion>

  <Accordion title="Can recipients add their own apps to my Collection?">
    Only if you grant them Editor permission. Default Viewer permission lets them use the apps but not modify the Collection.
  </Accordion>

  <Accordion title="Do permissions cascade to apps inside?">
    Yes. Sharing a Collection at Viewer level grants the recipient Viewer access to each app in the Collection. If you remove the Collection share, app access is removed too.
  </Accordion>

  <Accordion title="How do I unshare a Collection?">
    Open the Collection, click Share, find the recipient, and remove. Their access drops on their next visit. Activity history is preserved on your side.
  </Accordion>

  <Accordion title="What if an app inside a Collection is unpublished by its owner?">
    Recipients see a "no longer available" state for that app. The Collection stays. The app is no longer usable until it is published again.
  </Accordion>

  <Accordion title="Can I make a Collection public?">
    Public Collection sharing is supported. Set the visibility to Public and anyone on Playlab can find and use it.
  </Accordion>

  <Accordion title="Can a Collection contain another Collection?">
    Not in this release. A Collection holds apps. For nested groupings, use multiple Collections.
  </Accordion>

  <Accordion title="Is there a limit on apps per Collection?">
    No technical limit. Aim for fewer than 20 to keep the Collection readable for recipients.
  </Accordion>

  <Accordion title="Can I duplicate a Collection?">
    Yes. From the Collection's overview, click Duplicate. The copy is yours to modify independently.
  </Accordion>

  <Accordion title="What happens to shared Collections if my org is deleted?">
    Recipients lose access to the Collection and its apps. Org deletion is a hard action; coordinate with your Learning Partner before doing it.
  </Accordion>
</AccordionGroup>

***

Last updated: 06-05-2026

Contact us at [support@playlab.ai](mailto:support@playlab.ai)