Skip to main content
The order is fixed. You choose which screens appear by turning components on and off on the playtest’s Config tab. A playtest with no build, no keys, and no briefing goes straight from onboarding to the play period.

Getting on the roster

1

Onboarding

Your onboarding content, if you authored any. Otherwise the card opens on the checklist below.
2

Identity

The identity checklist. Always present, never optional.
3

NDA

Only appears when you turn on NDA. The player reads the terms, ticks any custom agreement boxes you added, and clicks I agree.
4

Screening

Only appears when you turn on Screening and the playtest’s access is open. Answers plus your eligibility rule decide whether the player continues.
5

Join

On an open playtest the join fires automatically once the gates above clear. On a closed playtest the player is already on the roster you seeded.
The NDA runs before screening, so a player never answers your questions only to discover there was an agreement to sign. Key vault redeem links follow the same order minus the NDA step, which only playtests have. Surveys and waitlists have their own onboarding flow without NDA or screening gates.

Inside a session

Objectives are not a separate screen. They render alongside the clock during the play period, so the player reads them while playing.

When recording is off

Turn off Gameplay Recording on the Config tab and the permission prompt, countdown, and review screen all drop out. The player gets Before you begin, which shows the minimum play time and a Start playing button, then the same running clock. Briefings, objectives, and your survey still appear, and the session still completes. A player who is offered screen and microphone as Optional and declines both lands in the same place: a timed play period with nothing captured.

Stopping early

End session is disabled until the minimum play time is reached. The usual way to end early is to stop screen sharing from the browser’s own control. That discards the recording and shows Session too short, which restarts the player to record the full minimum. The server also rejects under-length submissions as a backstop, though a normal client never triggers that.

Between sessions

A multi-session or longitudinal playtest shows Take a quick break with a countdown to the next session, then runs the same sequence again. When the last session wraps, the player gets That’s a wrap.

Gameplay recording

Set what a session captures, and whether screen and microphone are Required or Optional.

Player troubleshooting

What a player sees when one of these screens turns into a dead end.

Preview

Walk the whole flow yourself before you publish.

Session survey

Write the questions that close out a session.