Skip to main content
A submission is one player’s whole playtest, so it is the fastest way to answer a question about a specific person. Start there, then open the session that matters.

Take the guided tour

Follow one player through a playtest, from their answers to their sessions.

What you need first

  • Something to identify them by. The email address they joined with is the reliable one.
  • The playtest they took part in, if you know it. It narrows the search.

The playbook

1

Find their submission

Open Submissions in the sidebar, or the Submissions tab inside a playtest’s Results.Search by player email, and set the Status filter to show both completed and in-progress submissions.
The Submissions page shows Completed by default, so someone still mid-playtest can look missing until you widen the filter.

Submissions

How a player’s sessions add up to one submission, and what each status means.

Results

The playtest-scoped view of the same list, tab by tab.
2

Read where they got to

Open the submission.The status card shows their progress, such as 2 of 3 sessions completed, so you know whether you are looking at a finished run.
3

Open the session in question

Pick the session from the submission and open it.If they described something that happened on a particular day, the recorded date on each session narrows it quickly.
4

Read the session alongside the recording

Use the side panel tabs: Info for the device and capture settings, Transcript for what they said, Highlights for marked moments, Responses for their survey answers, and Events for what happened in your build.

Transcripts

Searching a transcript, and seeking the recording from a line.

Highlights

Generated moments, the categories behind them, and marking your own.
5

Check whether it was just them

Go back to the playtest’s Sessions tab and read Session details for the same session number.Browser, operating system, and screen size sit in that table, which is usually enough to tell a personal problem from a shared one.
6

Open their player record

Open Players in the sidebar and search the same email.Their record carries every playtest they have joined, their profile, and their Steam signals if they linked an account.

Players

The directory record behind every submission.

Player insights

The Steam signals on the record, and how fresh each one is.
7

Send it on if someone else needs it

Share the session, or the whole submission, from its share control.Sharing a submission gives the recipient the player’s full run rather than a single recording.

Sharing a session

The visibility modes, and what a public link exposes.

Roles and permissions

Who inside your studio can already open this without a link.

How you know it worked

  • The submission shows a session count that matches what the player told you.
  • Each session opens with its own transcript, highlights, and responses beside the recording.
  • The player’s record in the directory lists the playtests they have joined.
  • A shared link opens for someone outside your studio, and stops working once you close it again.

Submissions

How a player’s sessions add up to one submission, and what each status means.

Reviewing a session

The panel beside the recording, and the playback modes.

Players

The directory record behind every submission.

Share a session externally

Playbook: open a session or submission to someone outside the studio.