Skip to main content
A confidential playtest is an ordinary playtest with the leak paths closed one at a time. No public link, an agreement players accept before they answer anything, a hand-picked roster, and a short retention window. The tradeoff is self-serve recruitment: a closed playtest only admits people you seed.

Take the guided tour

Turn the NDA on and write the agreement players accept.

What you need first

  • A draft playtest. Most of what follows locks at the first publish.
  • The email addresses of the people you actually trust. A roster holds up to 1,000 players and needs at least one before Publish enables.
  • Your agreement wording, finished. The NDA freezes at publish, and unpublishing does not reopen it. A typo in a clause means a new playtest.

The playbook

1

Set access to Closed

On the Overview tab, find the Playtest Access card.
  • Click the Access card.
  • Choose Closed.
The self-join link goes away, and the Screening tab drops along with its Config row.
Do this first. It changes what the rest of the editor offers.

Access

What closing access removes, starting with the self-join link.

Screening players

The tab that disappears here, and why a closed roster does not need it.
2

Turn the NDA on

Open the Config tab and find the Playtest Settings card.
  • Set NDA to Enabled.
  • Click Save.
An NDA tab appears, pre-filled with a starter agreement.
3

Write the agreement

Open the NDA tab and edit the starter agreement.
  • Open the tab’s overflow menu.
  • Choose Custom checkboxes and add your own, up to 5 at 280 characters each.
The wording freezes at publish, and unpublishing does not reopen it. Read it once more before you go live.

NDA

The block editor, the checkbox limits, and how acceptances are stamped.

Preview the flow

Read the agreement as a player gets it, before the wording locks.
4

Seed a small roster

On the Players tab, click Add players, then pick how the addresses come in.
Type or paste addresses, one per line.
Every extra player is another copy of the build out in the world. Keep the list to people who need to be there.

Players

The roster tab, the 250 cap, and exactly what locks at publish.

Build a group you can reuse

Playbook: keep a vetted pool you can seed from every time.
5

Shorten the retention window

Go to Settings > Studio and set Retention period. The default is 1 month and the shortest is 1 week.
Retention is studio-wide. Shortening it here affects every playtest you have.

Data retention

What gets deleted when the window closes, and what survives it.

Decide how long to keep recordings

Playbook: pick the window, and export before it closes.
6

Publish

Click Publish in the editor header and confirm.Each acceptance is snapshotted against the player as they tick the boxes.

Requiring more than an email address

Each identity provider you add is another wall around the build, and another way to lose a tester. Turn one on only when you need it.
  • Open the Onboarding tab.
  • Click the fingerprint button in the section header.
  • In the Identities modal, switch on any of Email, Discord, Steam, and Google.
A player must connect every provider you switch on.

Sharing a session afterwards

A session set to Anyone with the link is accessible to anyone at all, with no account and no studio membership. Treat a shared session link as a copy of the recording.

How you know it worked

  • The editor has no Screening tab. The preview walks onboarding, identity, then the NDA, with no screening step.
  • The Players tab lists exactly the roster you seeded.
  • Each player’s row carries an NDA acceptance, stamped with the wording they agreed to.
  • Settings > Studio shows the retention period you chose, and sessions older than it stop appearing under Sessions.

NDA

The block editor, the checkbox limits, and why the agreement cannot be reworded after publish.

Data retention

What gets deleted when the window closes, and what survives it.

Sharing a session

Before you send anyone a recording: Sharing a session.

Run a closed playtest

The roster playbook this one builds on.