Statuses & How Things Work

This page is a quick reference for the statuses you’ll see across the dashboard, and for the work FirstLook does in the background after you take an action.

Player statuses

A player’s status tells you exactly how far they’ve progressed through your funnel — from first landing on your sign-up page to being fully onboarded. In lifecycle order:

Status	What it means
Pending	The player started sign-up but hasn’t completed it — for example, they haven’t confirmed their email yet or left sign-up steps unfinished.
Waitlist	The player completed sign-up and is on the waitlist, waiting for an invite.
Invited	An invite has been issued to the player (and the invite email sent, unless you suppressed it), but they haven’t accepted it yet.
Invite Accepted	The player accepted their invite and has started onboarding.
Email Confirmed	The player has confirmed their email address.
Provided Info	The player has filled in their profile information.
NDA Accepted	The player has accepted your NDA (if their role requires one).
Onboarded	The player finished onboarding. They receive everything attached to their role — keys, Discord roles, and access.

The statuses from Invite Accepted through NDA Accepted are the onboarding progression: each one marks the next step a player has completed after accepting their invite, until they reach Onboarded.

A few statuses sit outside this ladder:

Status	What it means
Deleted	The player was removed. Their personal data is wiped according to your retention policy.
Unlinked	The player hasn’t made a FirstLook account yet — typically a player created from the game via the SDK.
Merged	The player’s account was merged into another account.

For how players move from Waitlist to Invited — and which email is sent at each step — see How the waitlist and invites work. To filter your player list by state, see Players — note that the table above shows the display statuses, while the Players page filters use coarser underlying states: the whole Invite Accepted → NDA Accepted progression, for example, is a single “Accepted” state for filtering, so the list there is shorter.

Creator and campaign statuses

Creators have their own statuses — program statuses like Applied, Active, and Tracking, plus separate per-campaign participant statuses — and these are distinct from the player statuses above, even when a creator is also a player in your game. See Creator statuses for the full breakdown.

What happens in the background

Some actions in FirstLook don’t finish the moment you click confirm. Here’s what’s happening when things seem to take a while:

Bulk actions

Invites, role changes, and grants for large sets of players continue processing in the background after you confirm — the UI tells you when this happens. You don’t need to keep the page open, but a large batch can take a few minutes to complete. See Bulk Actions and Invite by Conditions.

Discord sync

Discord role changes and server joins are queued and processed separately from the FirstLook role assignment. The FirstLook role applies immediately; the Discord reflection can lag behind during sign-up surges. When a queue backs up, a Large Queue Processing banner appears in your dashboard, and players joining Discord during a surge see an estimated wait. See Discord setup.

Key assignment

Keys are assigned automatically when a player completes onboarding, drawn from the key pool attached to their role — there’s no manual step. See Getting Players Into Your Game.

Large key imports

Big key imports are processed in the background. The counts shown right after upload can look partial until processing completes — if you’ve just run a very large key import and the keys aren’t all appearing yet, give it a few minutes. See Keys.

Survey exports

Survey response exports are generated as files on demand when you request them. See Exporting Responses.