The basics
How Playlab is organized. Organization Your school, district, university, or partner. It holds members, apps, collections, and spaces. Most people belong to a single organization. See Navigating Playlab. Space A class, team, or group inside an organization, with its own members, apps, sessions, and building permissions. Organization Owners and Builders create spaces. Formerly called a workspace. See Creating and managing a space. App Something you build on Playlab. An app belongs to the organization it was created in, and you can add it to any number of spaces and collections without copying it. See Creating a Playlab app. Collection A curated set of apps you share as one resource, like a playlist. Adding an app to a collection creates a shortcut, not a copy. See What are Collections.People and roles
Playlab has three sets of roles. Owner, Editor, and User appear in more than one set, so these docs always say which one they mean, for example “organization Editor” or “app Editor”. Member Anyone in an organization or space. In a space, Member is also the name of a role (see Space roles). Student status Whether a member is a Student or Non-student. Set when you create an organization or space, when you invite members, or through rostering. Shown in the Student / Age column on the Members page. See Student status and ages. Age band The age range a student is in: Ages 13–15, Ages 16–17, Ages 18+, or Not sure. Playlab stores the age band, never a date of birth. An organization or space can have more than one. See Student status and ages. Group A named set of people you can share with or invite together. Groups are about people; collections are about apps. See Creating a group.Organization roles
Set on the Members page. See Organization roles.- Owner: manages the whole organization, including members, roles, and settings.
- Builder: creates apps, collections, and spaces, but can’t manage members. Formerly called Creator. (Lowercase “builder” means anyone building an app.)
- Editor: creates apps and collections, but not spaces. It doesn’t let them edit other people’s apps.
- User: uses apps, but can’t build. Formerly called Viewer.
- Space-only: sees only apps in the spaces they’ve been added to.
Space roles
Set on a space’s Members tab. See Space roles and permissions.- Owner: full control of the space. Usually its creator; the role can’t be changed or removed.
- Manager: the same control as an Owner, including archiving the space. Formerly called Facilitator.
- Member: uses the space’s apps, and may build or share if the space allows it. Formerly called Participant.
App and collection roles
Set in the Share dialog, one app or collection at a time. See Sharing with individuals.- Owner: everything an Editor can do, plus managing Owners and deleting.
- Editor: edits, publishes, and shares.
- User: uses it. Users can only be added once an app is published. Formerly called Viewer.
Building an app
Instructions What you write to shape how your app behaves, in the Build tab. Each save is a version. These docs used to call this the prompt. “Prompting” is still the name for the skill of writing good instructions. See Creating a Playlab app. Input and output An input is anything a user sends to your app. An output is what the AI sends back. Starter inputs Form fields a user fills in before a session starts, so the app has what it needs from the first message. See Adding starter inputs. References Files and links your app draws on, such as a curriculum document, a rubric, or a worked example. Pinned references are always loaded in full. Your organization’s shared references live in its reference library. See Adding references. Variability How creative or consistent your app’s outputs are, from 0% (most consistent) to 100% (most creative). The default is 70%. See Adjusting variability. Remix Making your own independent copy of an app to change as you like; the original stays as it was. App cards show how many times an app has been remixed. See When to remix anyway. Building permissions Four space-level toggles that control whether members can build apps, see each other’s apps, share apps outside the space, and manage their own apps. See Space building permissions.Sharing and publishing
These are two separate buttons in the app builder. Publish Chooses which version of your app people get when they open it. Publish puts your current version live, Publish changes updates it, and Unpublish takes it down. See Publishing your app. Share Chooses who can open or edit your app. In the Share dialog you pick a role for each person, group, or organization, then click Invite. See Sharing with individuals and Sharing with groups and orgs. General audience The setting in the Share dialog for who can open a published app: Only those invited, your organization, Playlab (anyone signed in to Playlab who has the link), or Public (anyone with the link). Replaces the older Private / Organization / Public visibility levels. Private by default Every new app is private to its Owner and your organization’s Owners until it’s shared or published. See App privacy and visibility. Cross-space use Adding the same app to several spaces without remixing it. Sessions stay separate per space, and updates flow from the original app. See Using an app across multiple classes.Sessions
Session Formerly called a conversation. See Reviewing session activity. Sessions Where sessions are reviewed: Admin → Sessions for everything in your organization, a space’s Sessions tab, and the Sessions tab in the app builder. Formerly called Activity. History Every session you’ve had yourself with any Playlab app, under History in the left sidebar. Replaces My Sessions. Flagged Marked for review because of a safety concern. Something can be flagged automatically by Playlab’s moderation (Moderated by Playlab) or reported by a user (Flagged by users). See Centralized org monitoring.Assistants
Playlab Assistant Playlab’s AI helper at the top of the left sidebar. It works across your apps: building new ones, reviewing existing ones, and analyzing how they’re used. See Playlab Assistant. Co-Builder The assistant panel inside the app builder, formerly called the Builder Assistant. It helps with the app you’re editing. See Co-Builder.Want a term added?
If you see a term in another doc that should be defined here, email [email protected] and we will add it.Last updated: 10-28-2026