// Security
End-User Access
How studios, studio members, and players access Userplay — authentication, roles, and data isolation.
Last updated May 31, 2026
Userplay has two distinct user types with different access models:
Studio members are authenticated users in a Userplay workspace. They design playtests and review the recordings and results. Studio members have Userplay accounts and sign in with email and password, a magic link, or a passkey, and can enable two-factor authentication.
Players are people invited to complete a playtest. A player establishes a lightweight player identity — email first, and optionally a linked Google, Steam, Discord, or passkey — with a self-reported profile, kept separate from any studio workspace. A player is never a member of a workspace: they receive a unique, signed link and see only the consent screen and the playtest itself.
Workspaces are the unit of data isolation. Members of one workspace cannot see another workspace’s data, and a player’s identity is never exposed to a workspace beyond what a playtest requires.
-
Recording Access
Where recordings are stored, who can access them, and how deletion works.
-
Playtest Recording
How Userplay captures, uploads, stores, and serves a playtest session from start to finish.
-
Player Privacy
How players participate in playtests — consent, what is captured, and what players can control.