Studio-defined account-registration questions (signup step two + admin review) #90

New Issue

2026-07-23T12:58:36Z

thatguygriff commented

2026-07-23 12:58:36 +00:00

Summary

Let the studio admin define account-registration questions that every new student must answer during signup, and surface each student's answers in the admin portal.

Requirements

Studio admin can author custom registration questions.
Questions are required on a second step of registration, after the student sets their name and password.
The admin student view shows a Registration Information section containing each student's answers.

Approach

Extend the existing Registration domain (which already stores answers polymorphically and is account-aware) rather than build a parallel system:

us_questions gains a scope column (offering | account) and a nullable offering_id; account answers reuse us_question_answers with registration_type = 'account'.
Authoring reuses the Offerings → Questions page via an "Account signup (all registrations)" scope (studio-admin only).
The [us_student_register] form becomes two steps (progressive enhancement; works without JS). Required answers are validated before the account is created; applies to all signup paths (invite, group link, self-approval).
StudentHistory::registrationInfo() powers a new Registration Information section on the student detail screen.

Requires a plugin version bump (1.0.0 → 1.1.0) so the schema migration runs.

## Summary Let the studio admin define **account-registration questions** that every new student must answer during signup, and surface each student's answers in the admin portal. ## Requirements - Studio admin can author custom registration questions. - Questions are **required on a second step** of registration, after the student sets their name and password. - The admin student view shows a **Registration Information** section containing each student's answers. ## Approach Extend the existing `Registration` domain (which already stores answers polymorphically and is `account`-aware) rather than build a parallel system: - `us_questions` gains a `scope` column (`offering` | `account`) and a nullable `offering_id`; account answers reuse `us_question_answers` with `registration_type = 'account'`. - Authoring reuses the **Offerings → Questions** page via an "Account signup (all registrations)" scope (studio-admin only). - The `[us_student_register]` form becomes two steps (progressive enhancement; works without JS). Required answers are validated before the account is created; applies to all signup paths (invite, group link, self-approval). - `StudentHistory::registrationInfo()` powers a new **Registration Information** section on the student detail screen. Requires a plugin version bump (1.0.0 → 1.1.0) so the schema migration runs.

thatguygriff referenced this issue from a commit

2026-07-23 13:44:33 +00:00

Add studio-defined account-registration questions

thatguygriff referenced a pull request that will close this issue

2026-07-23 13:45:48 +00:00

Studio-defined account-registration questions #91

thatguygriff closed this issue

2026-07-23 13:50:35 +00:00

Sign in to join this conversation.