Skip to main content
Screener questions can now be edited after publishing
Screener questions can now be edited any time after a project is published. It is important to note there are some catches.
  • When updated screener questions after publishing, the screener is effectively replaced
    • This means that if answers have already been collected, they are still qualified on the original screener
    • Only new screener responses will be qualified based on screener updates
We generally recommend using this only as a fallback if there was an error in screener setup or if no screener responses have been submitted. If you choose to accept edits after responses have been collected, you can use the createdAt field in the screener response to cross reference with the screener update time to manage different qualifications.

Question types and logic

The screener questionType can be selected from a set list of strings. Radio and checkbox answers can have additional answer logic and skip logic applied.
All projects require at least 2 screener questions to publish. On an external-screener project, the questions declared in externalQuestions count towards that minimum, so one screener question plus one external question is enough. Organizations enabled for screener-less projects are exempt: their projects publish with no screener questions at all, and participants apply without answering any. Ask your Respondent contact if you need this enabled.
Question and answer text fields accept plain strings only. HTML, Markdown, and other rich text formatting are not rendered — participants see the raw characters.
fileUpload, rank, and matrix are enabled per organization. Creating one of these question types without the corresponding feature enabled returns 403 Forbidden.

Basic screener question setup

POST /v1/projects/{projectId}/screener-questions The examples below show a basic setup for each question type.
  • For all examples isRequired is set to true and skipLogic is set to false
  • All question types can be required or not
  • Only radio and checkbox questions can include skip logic
    • These question types can also include an other option, but do not require it
    • The radio example shows the inclusion of an other option while checkbox example shows no other option
  • Each example shows the minimum fields required, but other fields may be available.

Checkbox qualification

A checkbox question qualifies a participant when both of these hold:
  • No selected answer is a Disqualify (answerValue: 3).
  • The Must Select answers (answerValue: 2) satisfy the question’s matchType:
    • "all" (the default when matchType is omitted): every Must Select answer must be selected.
    • "any": at least one Must Select answer must be selected.
May Select answers (answerValue: 1) never affect qualification. Selecting or skipping them changes nothing. A question with no Must Select answers qualifies on any selection that does not include a Disqualify answer. matchType is optional and only applies to checkbox questions. Questions created before the field existed have no matchType and behave as "all".
Checkbox with matchType
With "matchType": "any", selecting Figma alone qualifies. With "all" (or no matchType), the participant must select both Figma and Jira. Selecting Storybook disqualifies in either case.

Last modified on October 1, 2026