Admin Panel

Drag songs in the list to set the official order. Click + song name pills to add songs from the song library. Members can override the order with their personal practice order in the Music Library without affecting the official setlist.

These items appear on the member attire page as the standard kit for all gigs. Drag rows to reorder. Gig-specific modifications are set per-gig in the Gigs tab (Attire Notes field). Saving or reordering an item will ask to publish it to Firestore immediately — after the first confirmation this session, further attire edits publish automatically.

Signups from the public Request Access form land here. Approve writes status: "active" directly to Firestore. Reject deletes the signup permanently. Both take effect immediately — no Publish step needed. Requests flagged Other named an instrument outside the standard list and may need a score-master's attention before you approve them.

Members submit via Submit Music — either a MuseScore project file (.mscz) uploaded directly, or a link to a shared Drive/GitHub/Dropbox repository. Open the project file in MuseScore (or fetch it from the link) and use File → Export → Parts to get the actual .mxl/.pdf/.mp3 files, saving each with the suggested filename shown on the row, then drop them into music/{fileSlug}/ — create the song record first if this is a new song, then run the validator and deploy — see the SOP. Approve just marks a submission reviewed; it does not export files or touch Firestore song records for you. Reject keeps the record (for history) but marks it declined.

Any signed-in member can leave a note on a song's page — a wrong note in a part, a recording that needs redoing, anything at all — via the Notice Something That Needs Work? box. Notes land here as a simple to-do list; nothing changes on the song itself. Mark Done just flips the status (it doesn't fix anything for you); Delete removes a task permanently once it's actually handled.

Member records control access to the member portal. The email address must match the member's Google account exactly — it becomes the Firestore document ID. Any member with a record — active or pending — can sign in; status is shown to the member for personalization but does not gate access. Set status to inactive to revoke a former member's access. Saves here go to the session — click ↑ Publish to Firestore above to take effect (deletes are immediate, see the row's Delete button).