New
Every user on Playlab now has one organization responsible for them — usually their school or district.
That organization is the one accountable for how that person uses Playlab. The responsible organization sees their activity and is notified about safety flags, regardless of who built the apps they are using.
The short version: your organization is responsible for you, even when you’re using someone else’s app.
You don’t set this up, and most people never need to think about it. Playlab assigns it automatically. This page explains what it changes.
How it’s decided
What it means for you
Your own organization sees your activity — not whoever built the app.If you use an app that belongs to a different organization, your activity is still visible to the admin at your own school or district. It doesn’t disappear into someone else’s organization.If something you write gets flagged, the alert goes to your responsible organization.Safety notifications reach the right people at your own organization — people who can actually follow up rather than strangers who happen to own the app you were using.
Activity belongs to the user’s organization, not to your app.When someone from outside your organization uses an app you built, that conversation belongs to the organization responsible for them. It sits with their admin, not in your app’s activity view.Nothing changes for your own members.People in your own organization using your apps show up in your activity exactly as before. Anonymous, logged-out use of your apps is still attributed to your organization, since there’s no user to attribute it to.Building an app doesn’t grant you access to the people who use it. That’s the whole point — having access to someone’s activity and being accountable for that person are two different things.
You can see your members’ activity wherever they work on Playlab — including in apps owned by other organizations.Safety notifications and moderation digests about your people come to you. If a member of your organization is flagged in someone else’s app, your safety admin hear about it.Activity exports match the same scope, so an export reflects exactly what you can see on the page.You won’t learn other organizations’ names. If a user is the responsibility of an organization you don’t belong to, you’ll see that they have one, but not which one.
Questions
Can I change who’s responsible for someone?
Not from your own settings. Contact [email protected] and we’ll help.
What if someone belongs to two schools?
They’re assigned to one of them. If it’s the wrong one, contact support and we’ll pin it to the right organization.
Does this change who can use my apps?
No. This changes who is accountable for each user and who sees their activity. It doesn’t change app sharing, permissions, or access.
