Skip to main content
This page covers the create and share flow. For the concept, see Share with Collections.

​
How to create a Collection

1

Go to your organization

Open the org dashboard. Collections are an org-level container.
2

Open the Collections tab

The tab lists existing Collections in your org and shows a button to create a new one.
3

Click New Collection

The Create Collection form opens.
4

Name and describe

Pick a clear name. The description is for recipients to understand what the Collection contains.
5

Add apps

Click Add Apps. Search for apps you have access to and pick the ones to include. You can change the contents anytime.
6

Save

The Collection is created. You land on its overview page where you can manage apps and share.
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.

​
How to share a Collection

1

Open the Collection

Go to the Collection’s overview page.
2

Click Share

The Share button is in the top right.
3

Type the recipient

Add an individual, a group inside your org, or another organization. The recipient picker is the same as for app sharing.
4

Set permissions

Pick the permission level. For most cases, Viewer is the right level.
5

Send

The Collection appears in the recipient’s view. They can add it to workspaces or use the apps directly.

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

  • 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

​
FAQ

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.
Only if you grant them Editor permission. Default Viewer permission lets them use the apps but not modify the Collection.
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.
Open the Collection, click Share, find the recipient, and remove. Their access drops on their next visit. Activity history is preserved on your side.
Recipients see a “no longer available” state for that app. The Collection stays. The app is no longer usable until it is published again.
Public Collection sharing is supported. Set the visibility to Public and anyone on Playlab can find and use it.
Not in this release. A Collection holds apps. For nested groupings, use multiple Collections.
No technical limit. Aim for fewer than 20 to keep the Collection readable for recipients.
Yes. From the Collection’s overview, click Duplicate. The copy is yours to modify independently.
Recipients lose access to the Collection and its apps. Org deletion is a hard action; coordinate with your Learning Partner before doing it.
Last updated: 06-05-2026 Contact us at [email protected]