Admin sign in
Admin
| Code | School | Audition time | Town | Contacts | Login | Students |
|---|
Directors sign in with any of their district's codes (101 or 101a) and their district password. Passwords live only in the sign-in system, never in the database.
Coverage
| Level | Group | Instrument | Registered | Judges (sections) | Status |
|---|
Adjudicators
| Name | Level | Group | Instruments | Sections | Room |
|---|
Set where each instrument auditions. Students get their room when they check in; it shows on the registration table, in the judges' lists and as a tabulation filter. A group-wide room applies to every instrument in that group without its own room.
| Level | Group | Instrument | Room |
|---|
Coordinators run the registration table and tabulation. They can't change scores, rubrics, fees or event settings.
| Name | Role | This season |
|---|
Changes are saved as a draft while you work. Judges see them only after you publish; sheets already started keep their version.
Score reports for directors
Once auditions are scored, build a one-page summary of each student’s score sheet (every criterion and what the judge marked, total score, and placement). Directors download them as PDFs from Results & festival once results are published. Judges’ names are never shown. If a score changes later, build again.
Exports
Email directors
Everyone goes in BCC. Uses each school’s contacts (Schools tab, or the director’s own page).
Duplicate registrations
Write a message
{audition_time} becomes that school’s time. Blank lines start a new paragraph; links work; **bold** makes bold.Send to
Sent messages
npx firebase deploy --only functions). Waiting messages are not sent automatically afterwards; use Reuse to send them again.| Sent | Subject | To | Schools | Delivery |
|---|