Online

The waiting room is the point.

Every student gets a standing room on Microsoft Teams. Staff walk in; the family waits until somebody lets them in. What is said in there is kept, in your own Microsoft tenant.

A door, and two sides of it.

The lobby is not a formality here. It is the reason to have the room at all.

Anyone inside the studio’s Microsoft tenant joins without waiting — every teacher, the front desk, a manager. Everybody else is held: the student, the parent, a dial-in caller, somebody forwarded the link by a friend.

That is one setting, and it is the difference between a room a child can be alone in with whoever turned up, and a room somebody had to open.

A per-lesson meeting is stricter still — only the organizer walks in. The standing room is deliberately looser at the staff end, because a teacher who had to wait in the lobby of their own lesson until the owner admitted them would be worse than useless.

The chat is the record.

A per-lesson meeting evaporates when the call ends. A standing room accumulates.

A term of sheet-music links, homework, corrections and “can we move Thursday” in one thread the family can scroll back through — rather than thirty separate dead meetings, each with three messages in it that nobody can find again.

It is also the better answer for safeguarding. What an adult said to a child is retained in the studio’s own tenant, under the studio’s own retention rules, and can be looked at. The alternative is not privacy; it is an absence of evidence in both directions.

Check Microsoft before a child finds out.

The permission a studio grants is usually not the one that blocks this.

Creating meetings needs a consent most people make correctly. Putting a waiting room on a teacher’s meeting needs something else — a Teams application access policy, granted per user in PowerShell. Without it, the Microsoft admin screen shows the permission consented while every lesson meeting silently has no lobby at all.

A studio in that state believes it is protected and is not. So Teachers carries a Check Microsoft button per teacher, and it reports the two grants separately, because they fail independently and for unrelated reasons. One combined tick would send somebody off to fix the half that already worked. A refusal names the policy that is missing.

What else is in here.

  • The room belongs to the studio

    Not to the teacher who happens to teach that student this term. A teacher leaving does not take a family’s lesson room, or a term of what was said in it, out of the door with them.

  • A quiet student keeps their room

    Microsoft expires an online meeting sixty days after it was last used. A student who stops for an exam term would come back to a dead link and a lost term of chat, so a room quiet for thirty days is re-asserted before that can happen.

  • Nobody is recorded by accident

    Automatic recording is off, and entry and exit are announced. Whoever is in the room with a child can be heard arriving.

  • The student cannot take the screen

    Presenting is staff-only until a teacher hands it over in the moment. A child cannot share their screen with the room because they found the button.

  • Online rooms do not double-book

    A physical room holds one lesson at a time and the scheduler enforces it. A room marked online can hold as many as you like, because it is not a room — the same clash check, told the truth about what it is checking.

  • One link, in the places a family looks

    The join link sits on the lesson in the schedule and in the family’s portal, rather than being pasted into an email each week and hunted for on the day.

It is not generally available yet.

B♭ Studio runs a working music studio today. If you run one too, tell us about it and we will get in touch when there is something to show you.

Join the early access list