Local devWrites to the question bank require the admin/rutgers role. On the emulator, sign in as the seeded dev admin so saves pass Firestore rules.
Add, edit, delete, or reorder the onboarding questions. Saving creates a new version — participants already onboarded keep the version they answered; new participants get the new one. Every save is logged. (In production this screen is restricted to the Rutgers/clinician role via Firestore rules. Changing a clinical instrument during an active trial may require IRB review.)
Tip: the Help / info text becomes the ⓘ tooltip a participant sees; use Allow "Other" write-in, the "please explain" prompt, and — new in this version — a number Min/Max, a per-question Default answer, and Lock answer to pre-set and freeze a response.
🧭GUIDOHi! I'm your guide. I'll pop up little tips as you build. Toggle me off any time.
Describe a question AI-assisted
Type it plainly and I'll draft a question for you to review — e.g. "ask about nightmares; if yes, ask how often per week." You always review & edit before saving. (Needs the local key; without it you'll get a starter template.)
0 questions · active v-
PREVIEW — this is how participants will see it (unsaved edits included)
Checks whether every required field has an entry (as if the participant clicked Finish) and highlights any left blank. (Close always exits freely.)