Skip to main content
Every playtest, survey, and waitlist keeps its own roster, and any of them can be imported into a new playtest. Testing a second build with the people who saw the first one takes a few clicks.

Take the guided tour

Walk the roster of a closed playtest and invite specific players onto it.

What you need first

  • A playtest, survey, or waitlist you have already run, with people on its roster.
  • A new build worth bringing them back for, and something to tell them about what changed.

The playbook

1

Create the new playtest

Create it as usual, then set Playtest Access to Closed on the Overview tab.Closed access means only the people you add can join, which is what makes an invited roster meaningful.

Playtest access

Open against closed, and why this job needs closed.

Run a closed playtest

Playbook: the roster-only playtest this one builds on.
2

Open the roster

Open the Players tab in the playtest editor.A closed playtest has a roster from the moment it is a draft, so you can fill it before publishing.
3

Import the old roster

Click Add players, then From group.Pick the group behind the playtest you ran before. Options are badged Custom, Playtest, Survey, and Waitlist, so a previous playtest’s roster is easy to spot.

Player groups

The rosters your playtests, surveys, and waitlists keep for themselves.

Build a group you can reuse

Playbook: keep a custom pool instead of importing a whole past playtest.
4

Add anyone else you want in

Import more than one group in the same pass, or add addresses by email or CSV.Duplicates resolve to one player record, so overlapping rosters are safe to combine.
Players you add by hand skip screening. If you need them screened, recruit them through a waitlist instead.

Adding players

Every way onto a roster, and what each one skips.

Recruit with a waitlist

Playbook: the front door that screens people on the way in.
5

Trim the list

Remove anyone you do not want back before you publish.Removing someone from this roster takes them out of the playtest, not out of your directory.
6

Publish and tell them

Publish the playtest, then hand out the link or announce it where this group already talks to you.Say what changed since last time. A returning tester wants to know why they are being asked again.

Launch a playtest

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

Session briefing

Where to say what changed, so returning testers read it in the flow.

Picking the right roster to import

How you know it worked

  • The playtest’s Players tab lists the imported members before you publish.
  • The source group still holds everyone it did, since importing copies rather than moves.
  • Adding the same group twice adds nobody new.

Adding players

Every way onto a roster, and what each one skips.

Playtest access

Open against closed, and why this job needs closed.

Player groups

The rosters your playtests, surveys, and waitlists keep for themselves.

Sort players into groups

Playbook: build a narrower roster than a whole past playtest.