Skip to content

Ensembles

A group that people join, not one they get put in.

A choir, a quartet, a band, a worship team. Any account creates one, invites the members, and shares the music. No teacher, no plan, no cost.

What it looks like

The roster and the shelf, in one place.

An ensemble has a member list with each person's instrument, and a library shared with the whole group. That is what a member sees when they open it.

  • Each member carries the instrument they play, so a section list is a real section list.
  • Music shared with the group sits on one shelf everyone reads from.
  • The creator is a member from the start, since they are the one who made it.
An ensemble page with a member list showing instruments and a shared music library.
A seeded ensemble. Members with their instruments, and the group's shared music underneath.

How it actually works

Three mechanisms, each one provable in the app.

Create and invite

Any account makes a group and invites members by the email of an account that already exists, who get an email inviting them to accept. There is no role gate: teacher or student, you can run one. For a whole section, share a single join link instead and let people join by clicking it.

Accept, or do not

An invitation grants nothing until the person accepts it. A pending invitee sees none of the group and the group sees none of them. Declining is allowed, blocks nothing, and can be reversed by a fresh invitation later. Any member can leave whenever they like.

Share and attribute

Share a piece with the ensemble and it is on every member’s shelf. A member can tag a practice session to the group for their own records. Nobody, leader included, sees anyone else’s practice log. The tag is attribution, not sharing.

The boundary

What it does not do, up front.

The honest edge, so you find it here rather than after moving a section onto it.

  • A piece belongs to one ensemble at a time.
  • A member who leaves loses access; the group’s shared music stays.
  • It is free because there is no billing system, and it is a small new project.

Not built

  • A leader view of members’ practice, or a read-receipt on the music.
  • Storage suitable for licensed or rented parts; files sit at public URLs.
  • Calendar sync to Google or Apple; events and RSVPs live in the app.
  • Recurring events; a weekly rehearsal is entered one date at a time.
Naming these is cheaper for both of us than a page that implies otherwise.

The rehearsals live next door.

A group needs a schedule as much as a shelf. The calendar carries the rehearsals, with an attendee list on each one.

Start a group and share one piece.

Make an ensemble, invite a couple of people, and put a rehearsal on the calendar.