Skip to main content
Players do everything in the browser. They open a link you share, prove the identities you require, and play. Signing in creates their Userplay player account, which they can return to later at the player portal. Each link runs a slightly different sequence. Only the playtest link can carry an NDA.

Before they play

Onboarding shows whatever content you authored, then moves to the identity checklist. Identity is mandatory on every surface and cannot be turned off. When you turn on an NDA, it appears after identity and before screening. That way consent is settled before you ask a single question. Screening runs last, and on a playtest it only runs when access is set to open. Closed rosters are invited, not screened.

While they play

Once a player is on the roster, the session flow takes over: any build or key hand-off, a briefing, the play period, a survey, and a confirmation. Sessions in a multi-session or longitudinal playtest are separated by a cooldown screen.

What they have to install

Nothing. The flow runs entirely in the browser. Players need Chrome, Edge, or Firefox, and a player on an unsupported browser is told so.

Next steps

Identity

The checklist that decides whether a player gets past onboarding.

Session flow

Every screen from the build hand-off to the confirmation, in order.

Player portal

Where players pick a playtest back up and manage their linked accounts.

Troubleshooting

Match what a stuck player describes to the screen they actually saw.