> ## 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.
# Using an app across multiple classes
> How to use a single Playlab app in several spaces without remixing, with activity segmented per class.
New
You can add the same app to as many spaces as you need. The app keeps a single owner and source of truth. Each space's **Sessions** tab shows only sessions by that space's current members, plus logged-out sessions. When an update is published, every class using the app gets the new version.
This is how you share an app with a space. Spaces don't appear in the app's **Share** dialog, so you start from the space and add the app there.
The app exists once. Adding it to a space puts its card on the space's **Apps** tab, and members can launch it once it's published. The app itself stays with its original owner.
## How to add an app to a space
**1. Go to the space**
Open the space where you want the app available. You need to be its Owner or Manager.
**2. Click Add apps**
In the top right of the space, click **Add apps** and choose **Add existing apps or collections**. A dialog titled **Add apps and collections to** your space's name opens, with **Apps** and **Collections** tabs and a search field.
**3. Select an existing app**
Pick the app from the list or search by name. Apps from your org, apps shared with you, and apps in Collections you have access to all appear here. Then click the add button, which counts your picks (for example, **Add 2 apps**).
**4. Confirm**
The app shows up on the space's **Apps** tab. Members find it when they open the space, under **All**.
To add the same app to another space, go to that space and repeat the steps.
## Activity is segmented per class
Each space where the app is added has its own **Sessions** tab. It shows sessions on the space's apps by the space's current members, plus logged-out sessions. Sessions aren't tied to the space they started in: a student who belongs to two spaces with the same app shows up in both, and a student removed from a space drops out of its Sessions tab. A teacher running three sections in three spaces sees three Sessions tabs, one per section. Org Owners can see sessions across the organization.
```mermaid theme={null}
graph TD
App["✏️ One app
(owned by you)"]
WS1["📁 Class A"]
WS2["📁 Class B"]
WS3["📁 Class C"]
Act1["📊 Activity A"]
Act2["📊 Activity B"]
Act3["📊 Activity C"]
App -.added to.-> WS1
App -.added to.-> WS2
App -.added to.-> WS3
WS1 --> Act1
WS2 --> Act2
WS3 --> Act3
classDef app fill:#a4beeb,stroke:#0c0f14,stroke-width:2px,color:#0c0f14
classDef ws fill:#fbf9f6,stroke:#0c0f14,stroke-width:1px,color:#0c0f14
classDef act fill:#feffa0,stroke:#0c0f14,stroke-width:1px,color:#0c0f14
class App app
class WS1,WS2,WS3 ws
class Act1,Act2,Act3 act
```
*One app, three classes, three separate Sessions tabs. Each teacher sees only their class.*
For more, see [Reviewing session activity](https://learn.playlab.ai/getstarted/Reviewing%20Activity).
## Updates propagate automatically
Edits reach the spaces only when they're published. After someone clicks **Publish changes** in the builder, new sessions in every space use the latest version. Earlier sessions are kept.
This is the main advantage over remixing: a small fix or a curriculum update doesn't need to be copied into ten places.
## When to remix anyway
Cross-space use covers most cases. Remixing still makes sense in a few:
**Heavy customization.** If you want to substantially change the prompt, references, or starter inputs for one class, remix. The original app stays clean.
**Frozen-in-time pedagogy.** If you want a class to use the app exactly as it was at a point in time, even if the owner ships updates, remix. Your copy is independent.
**Learning the prompt.** Students learning to build apps often remix as a way of seeing how an app is built. The remix is for teaching, more than for production deployment.
For most other cases, adding the app to the space is the simpler path.
## Key points
> [!NOTE]
>
> * Add the same app to as many spaces as you need; no remixing
> * Each space's Sessions tab shows its own members' sessions
> * Published updates reach every space automatically
## FAQ
> [accordion] Can students see each other across classes?
>
> No. Members see only their own sessions, in **History**. A space's **Sessions** tab is for its Owners and Managers.
> [accordion] Does this replace remixing entirely?
>
> For deployment, mostly. For pedagogy and customization, no. Remixing is still useful for the cases above.
> [accordion] Who sees the activity?
>
> A space's Owners and Managers see its **Sessions** tab: sessions on the space's apps by current space members, plus logged-out sessions. Members see only their own sessions in **History**. Org Owners can see sessions across the organization, and the app's Owners and Editors can review sessions by people who share an organization with them from the app's **Sessions** tab.
> [accordion] What if the original app is unpublished or deleted?
>
> If it's unpublished, its card stays in the space but has no **Launch** button until it's published again. If it's archived, it disappears from the space, and its sessions no longer show in the space's **Sessions** tab. Either way, members keep their past sessions in **History**.
> [accordion] Can I remove the app from a space later?
>
> Yes. Space Owners and Managers can open the app card's menu (**⋮**) and choose **Remove from space**. The app isn't deleted, but its sessions no longer show in that space's **Sessions** tab.
> [accordion] If I update the app, do all classes get the update at the same time?
>
> Yes, once you publish the changes. New sessions in every space use the latest published version.
> [accordion] Does cross-space use count against any quota?
>
> No. Playlab doesn't limit how many apps a space can have or how many spaces an app can be in.
***
Last updated: 10-28-2026
Contact us at [support@playlab.ai](mailto:support@playlab.ai)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.