Skip to main content
A closed playtest has no self-join link. Only the people on the email roster you seed can get in. You need at least one player on that roster before you can publish, the roster locks the moment it goes live, and there is nobody to screen because you already chose them.

Take the guided tour

Walk the create flow in the studio and seed the first roster as you go.

What you need first

  • The email addresses. There is no link to fall back on if the list turns out thin.
  • A roster size you have the balance for. The reservation at publish is roster size multiplied by session count. Check the Credits card under Settings > Billing.
  • Optionally, a player group you can import instead of pasting the same emails into every playtest.

The playbook

1

Set access to Closed

On the Overview tab, find the Playtest Access card.
  • Click the Access card.
  • Choose Closed, so only people you add by email can join.
The Screening tab disappears, along with the Screening row on Config.
The Access card is draft only. A roster you picked by hand has nothing left to screen for.
2

Seed the roster

On the Players tab, click Add players, then pick how the addresses come in.
Paste addresses, one per line.
Duplicates are skipped.

Build a group you can reuse

Playbook: create the pool the From group tab draws on.

Adding players

The import methods, the caps, and how duplicates are matched.
3

Configure the rest of the playtest

Set type, timing, build, keys, briefing, and survey on their own tabs.
None of them depend on access. A closed playtest can be single, multi, or longitudinal.

Playtest types

What each type commits you to, and which parts stop being editable.

Gameplay recording

The capture streams and highlight categories behind the Recording tab.
4

Check the roster one last time

Read the Players tab through before you publish.
You cannot remove anyone after the first publish, and unpublishing does not give that back. Adding someone you forgot means an unpublish, which changes the reservation.

Players

The roster tab, and exactly what locks the moment you go live.

Unpublishing

What comes back when you take a live playtest down, and what does not.
5

Publish

Click Publish in the editor header and confirm.
Publish stays greyed out until the roster has at least one player. Hover it for an Almost there popover listing Add at least 1 player, and click that row to jump to the Players tab.

Publishing

Every requirement the button checks, and what it reserves.

Launch a playtest

Playbook: preview, publish, share the link, announce it.

How you know it worked

  • Your playtest reads as closed, admitting only the people you add by email.
  • There is no Screening tab in the editor and no Screening row on Config.
  • The Players tab is an editable roster while the playtest is a draft, and reads “Unpublish to add or remove players.” once it goes live.
  • Players who reach the playtest walk onboarding and identity but are never asked a screening question. Confirm this in the preview.

Players

The roster tab, the import methods, and exactly what locks at publish.

Player groups

Build the list once and reuse it across playtests.

Run an open playtest

The alternative when you want the link to do the recruiting.

Access

Open and closed modes, and what each one changes.