Skip to main content
Every quest has a Participants page where researchers can view enrolled participants, update their lifecycle status, and assign them to cohorts. This is the primary operational surface for managing a study’s participant roster.

Accessing the Participants Page

  1. Open your quest detail page
  2. Click Manage Participants in the action bar
  3. The participants page opens at /quest/<guid>/participants
Only quest editors (the quest creator, organization members with quest.update permission, or listed collaborators) can access the participants page.

The Participant Table

The participants table shows every person who has joined the quest. Each row includes:
ColumnDescription
ParticipantUsername, email, or public key — whichever is available. A secondary identifier is shown below.
CohortThe cohort the participant belongs to, or “Unassigned”. Editable via dropdown.
StatusThe participant’s current lifecycle status, shown as a colored badge. Editable via dropdown.
JoinedWhen the participant joined the quest.
Last status updateWhen the status was last changed.
Changes to status and cohort save immediately — there is no separate save button.

Participant Statuses

Participants move through a lifecycle of statuses. Each status has a distinct color badge for quick visual identification:
StatusColorDescription
ScreenedGrayParticipant has been reviewed for eligibility
EligibleCyanMeets eligibility criteria
IneligibleAmberDoes not meet eligibility criteria
ConsentedVioletHas provided informed consent
EnrolledGrayJoined the quest (default status on join)
ActiveBlueCurrently participating in the study
CompletedGreenFinished all study activities
WithdrawnRedWithdrew from the study
ExcludedRoseRemoved from the study by the researcher

Automatic Enrollment

When a participant joins a quest, they are automatically created as a QuestSubject with enrolled status. No manual action is needed — the participant appears in the table as soon as they complete the join flow.

Changing Status

Select a new status from the dropdown in the Status column. The update is sent to the server immediately. Use this to track participant progress through your study protocol — for example, moving participants from enrolledactivecompleted.

Cohorts

Cohorts let you organize participants into groups — useful for multi-arm studies, A/B conditions, treatment vs. control groups, or any grouping your study design requires.

Creating Cohorts

Cohorts are created via the API:
POST /api/quest/:questGuid/cohorts
{
  "name": "Treatment Group A",
  "description": "Participants receiving the active intervention"
}
Each cohort has a name (required) and an optional description.

Assigning Participants to Cohorts

In the participants table, use the Cohort dropdown to assign or reassign a participant. Select “Unassigned” to remove the cohort assignment. Changes save immediately.

Filtering

The participants page includes two filters above the table:
  • Filter by status — show only participants with a specific status (e.g., only “Active” participants)
  • Filter by cohort — show only participants in a specific cohort, or those who are “Unassigned”
Filters can be combined — for example, show all “Active” participants in “Treatment Group A”.

Refreshing Data

Click Refresh participants to reload the participant list from the server. This is useful when participants are actively joining and you want to see the latest roster.

API Reference

All participant operations are available via the REST API for programmatic access:
MethodEndpointDescription
GET/api/quest/:questGuid/subjectsList all participants. Supports ?status= and ?cohortGuid= query filters. Use cohortGuid=unassigned for unassigned participants.
PATCH/api/quest/:questGuid/subjects/:subjectGuid/statusUpdate a participant’s status. Body: { "status": "active" }
PATCH/api/quest/:questGuid/subjects/:subjectGuid/cohortAssign a participant to a cohort. Body: { "cohortGuid": "..." } or { "cohortGuid": null } to unassign.
GET/api/quest/:questGuid/cohortsList all cohorts for a quest.
POST/api/quest/:questGuid/cohortsCreate a new cohort. Body: { "name": "...", "description": "..." }
All endpoints require authentication and editor-level access to the quest.

Next Steps