Waiting room, lock, and who may in

Decide who gets in before they are in

A waiting room with knock and admit, a lock, a passcode, a restriction by email domain, and a say in whether anybody may arrive before the host.

What it is

Five separate controls, because they answer five different worries. The waiting room holds people until somebody admits them. The lock stops anybody else arriving at all. A passcode gates the link itself. An email-domain restriction refuses anybody from outside your organisation. And join-before-host decides whether the meeting can start without you.

They are set per meeting, and they are enforced by the server rather than by the interface. Refusing somebody in the browser is a suggestion; this is a refusal at the door that issues the credential.

Knocking is recorded

A waiting room needs to know somebody is waiting, which sounds obvious and is the part most implementations get wrong. A knock is written down when the token endpoint refuses entry, so the host sees a name rather than an empty list.

Read next

  • People with no account

    Open the meeting to guests, copy a link, and close it again — all from inside, while the person you are trying to let in is still waiting.

  • How people arrive

    Muted or not, camera on or off, who may unmute, who may share a screen, who may chat — set per meeting, enforced on the server.

  • Moderator controls

    Mute everybody, mute one person, remove somebody, lock the door — reachable in one press, because by the time you need them you are not reading.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    Waiting room, lock, and who may in — SeeUAll · SeeUAll