This guide is for people coming from the previous version of Playlab. It will be retired in August 2026 once everyone has migrated. For current Playlab guidance, see Learn on Your Own or Feature Documentation.
This page is updated on the same schedule as the engineering rollout. Last review: 2026-06-17.
Currently in flight
These are rolling out now or scheduled for the coming weeks. Org-level insights aggregation. Cross-workspace metrics aggregated for org admins. The org dashboard is live and the aggregated views are rolling out — check the product changelog for current status. Network and district page. A view designed for partners deploying Playlab across multiple organizations. In design and scoping. Ships after the org-level insights work.Recently shipped: the per-app builder insights view — total users, sessions, average conversation length, and engagement over time for the apps you own, with a date-range filter. See App-level insights for builders.
Not yet available
These are known gaps that the current release does not address. They are tracked and on the roadmap, with no committed date. Rostering support. Several partner districts use Clever or ClassLink to provision accounts and class rosters into Playlab. The existing rostering integrations keep working, but new rostering features are not yet added. Districts that depend on rostering for class setup should coordinate migration timing with the Playlab team. Org-level starter input templates. Standardizing starter inputs across an org’s apps is not yet supported. Each app sets its own. Large districts have asked for this; it is on the roadmap. Dedicated network deployer role. Partners who push Playlab into schools they don’t directly control can do this today through cross-org sharing plus Collections, but a bespoke deployer role with its own permissions is not built yet. White-labeling and custom branding. District-wide visual customization is not available yet. Foundational work is in progress. Custom org-level roles. Playlab ships with the five standard roles (Owner, Creator, Editor, Viewer, Workspace-only). Custom role definition is planned but not in this release. See Org permissions and roles. Adding a group directly to a workspace. Temporarily unavailable while we improve how groups and workspaces work together. To get a whole team into a workspace today, set up the workspaces (and groups) on an organization invitation. App-to-app links and embeds. Playlab does not support directly linking from one Playlab app to another in a way the AI can navigate. Apps stand alone. Cross-app context is shared through references.Workarounds today
A few patterns that work while the above ship: For network deployment across many orgs: use cross-org sharing plus Collections — build a Collection once and share it with each partner org. For org-level starter inputs: set them in each app individually. Bulk update is on the way. For custom roles: use the five standard roles and document any per-person nuance separately.How to give feedback
If something on this page is blocking you, or if you want to nominate something we have missed, email [email protected]. For roadmap updates and ship dates as they’re confirmed, watch the Q2 2026 changelog and the broader product changelog.Last updated: 06-26-2026 Contact us at [email protected]