Allow one name change: the participant checks or changes the name, then confirms it. Confirmation locks the name. No name change — use portal name: the accepted portal entry is printed as-is, including a staff ID or ticket code if that was entered. There is no certificate-name editing. Existing confirmed certificates keep their names.
Keep your Google Sheet sharing Restricted and stop any Publish to web publication. Participant certificate details stay in the private Sheet; certificate design and wording come from BlitzTrials. Existing certificate links keep their original Sheet, so retain its records and access.
Connect with Google, approve the Google account that owns your Sheet, then choose that file. No Apps Script deployment or connection key is needed. Return here and refresh the list. You can connect a Sheet before saving a new study.
For an existing deployed Apps Script service only: run blitzCertificateStorageConnection in its Apps Script project, copy the settings, paste them here and check the connection. Keep the existing deployment, key and old records. New connections should use Connect Google Sheet.
Add the questionnaires in the order participants should see them. B1 means the first questionnaire, B2 the second, and so on. In routing rules, B1.Q3 means Question 3 in B1. A questionnaire cannot be selected twice.
Show point-value rules to participants. Leave this off when revealing scores could influence answers.
Choose where participants go next based on an answer or score. Use one rule per line. Examples: B1.Q3 == A => GO_BANK_2 HADS-A >= 11 => GO_BANK_2 TOTAL < 50 => END_TEST B2.Q1 == YES => SCREEN_OUT TIME > 300 => END_TEST Use >=, <=, >, <, == or !=. Questionnaire references use B1, B2 and so on.
Limit accepted responses that meet a condition. Use one rule per line: condition => maximum. Zero excludes matching responses. Examples: TIME < 600 => 0 B1.Q1 == "A" => 30
Close the study to further accepted submissions after this total. Leave blank for no overall limit. Other account and study limits still apply.
Normally participants see why a submission was rejected. Turn this on to show a general notice instead. It does not change whether the submission is accepted.
Choose an access-code batch for participant login. Allow each code more than once only when the same participant should be permitted to return under your study rules.
Paste the pre-filled response link from your form setup. It must contain MAGIC_ID and MAGIC_RESULT in two different fields. These placeholders are replaced with participant identification and results. A Google Forms pre-filled link is supported.
Send results to the configured form in the background. Turn this off when participants must open the form and press Submit themselves. A failed send can require a retry; avoid restarting the assessment.