> ## 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.

# Sharing a Collection

> Share a Collection with people, groups, or organizations, and set who can view, edit, or own it.

Once you've [created a Collection](/getstarted/Creating%20a%20Collection), sharing it hands the whole bundle to others as a single resource. Sharing works just like sharing an app: add recipients, set a role, done.

## How to share a Collection

<Steps>
  <Step title="Open the Collection and click Share" icon="share">
    The **Share** button is on the Collection's page.
  </Step>

  <Step title="Add a recipient" icon="user-plus">
    In **Search for name or emails**, add a person, a group in your org, or another organization. Recipients are grouped under **Users with access** and **Groups with access**.
  </Step>

  <Step title="Set each recipient's role" icon="user-check">
    Choose from the role dropdown — **Viewer**, **Editor**, or **Owner** (see below). Pick **Remove access** to revoke someone.
  </Step>

  <Step title="Done" icon="check">
    The Collection appears in each recipient's view, ready to add to a workspace or use directly.
  </Step>
</Steps>

<Frame caption="The Share dialog for a Collection: add people or groups, then set each one's role — Viewer, Editor, or Owner.">
  <img src="https://mintcdn.com/playlabai/N_qf0YRGPeXGUWqu/images/v2/collectionpermissions.png?fit=max&auto=format&n=N_qf0YRGPeXGUWqu&q=85&s=2039a7d49c6cb4f4b532e37d9a0e5abf" alt="The Share Collection dialog with a 'Search for name or emails' field, the collection creator, a Groups with access section showing a group set to Viewer, a Users with access section, and an open role dropdown listing Owner, Editor, Viewer, and Remove access with descriptions." width="500" className="mx-auto" data-path="images/v2/collectionpermissions.png" />
</Frame>

## Permission levels

| Role       | Can do                                               |
| ---------- | ---------------------------------------------------- |
| **Viewer** | View and launch the apps in the Collection           |
| **Editor** | Add or remove apps, and share the Collection         |
| **Owner**  | Add or remove apps, share, and delete the Collection |

Most recipients should be **Viewers** — they get the apps without being able to change the bundle. Reserve **Editor** for trusted partners who co-curate, and **Owner** for co-leads who need full control.

## Sharing with groups and orgs

Sharing with a **group** reaches everyone in it at once — pair a curated app bundle with a whole team by sharing a Collection with a [Group](/getstarted/Creating%20a%20Group). Sharing with an **organization** reaches that whole org, with activity kept segmented per org. This is how partners deploy a starter pack across many districts at once.

<Tip>
  You don't re-share when you change a Collection. Add or remove apps and recipients see the new set on their next visit — and when an app's owner publishes a new version, that flows through too.
</Tip>

For cross-org deployment, permission cascade, and curation depth, see [Creating and sharing a Collection](/features/collections/Creating%20and%20Sharing%20a%20Collection), [Curating a Collection](/features/collections/Curating%20a%20Collection), and [Using a shared Collection](/features/collections/Using%20a%20Shared%20Collection).

## Key points

<Info>
  * Share a Collection the same way you share an app — with people, groups, or whole orgs
  * Roles: **Viewer** (use), **Editor** (curate & share), **Owner** (full control, incl. delete)
  * Change a Collection's apps anytime; recipients see updates without re-sharing
</Info>

## FAQ

<AccordionGroup>
  <Accordion title="What permission should most recipients get?">
    Viewer. It lets people use the apps without changing the Collection. Editor and Owner can modify the bundle, so reserve them for co-curators and co-leads.
  </Accordion>

  <Accordion title="Do recipients get updates when I change the Collection?">
    Yes. Add or remove apps and recipients see the new set on their next visit — no re-sharing needed. New published versions of the apps inside flow through too.
  </Accordion>

  <Accordion title="How do I stop sharing with someone?">
    Open the Share dialog, find the person or group, and choose **Remove access** from their role dropdown.
  </Accordion>

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

  <Accordion title="What's the difference between sharing a Collection and sharing each app?">
    A Collection is one resource you share once. Recipients get every app inside at the role you set, and the bundle stays in sync as you change it — no per-app sharing or re-sharing.
  </Accordion>
</AccordionGroup>

***

Last updated: 05-27-2026

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