Skip to main content
Archiving takes the playtest, its roster, its key vault, its sessions, and its submissions out of your lists together. The order matters: export first, archive second.

What you need first

  • A playtest you are finished with.
  • Somewhere for the findings to live outside Userplay: a doc, a ticket tracker, a folder.

The playbook

1

Read it back while you still can

Open the playtest’s Results page and work through the sessions.

Results

Every tab on the results page, and which ones your playtest earned.

Work out what to fix next

Playbook: read the sessions before the data goes out of reach.
2

Export what you need

Use Export in two places.
  • On the results kebab, for the playtest-wide datasets.
  • On individual sessions, for video, audio, transcripts, highlights, and events.
Session media is deleted on your retention period, which may already have passed. Export the survivors now.

Exports

Every dataset, and which ones are playtest-scope versus session-scope.

Export your playtest data

Playbook: pull both scopes out before the window closes.
3

Archive it

From the Playtests list, open the card’s overflow menu and click Archive.Type the playtest’s exact name to confirm.
There is no undo. If there is any chance you want the data back, unpublish instead. It returns the same unused credits and leaves everything readable.

How you know it worked

  • Your recording balance went up by the unused portion of the reservation.
  • The playtest is gone from Playtests, and its sessions are gone from Sessions.
  • Your playtest usage meter dropped by one.
  • Any Discord announcement for it has been removed from your server.

Archiving a playtest

What goes, what refunds, and why there is no undo.

Unpublishing a playtest

The reversible version of the same refund.

Work out what to fix next

Do this before you archive, not after.

Exports

Every dataset, and which ones are playtest-scope versus session-scope.