Require manual director approval before guests can join a claimed room.
Director Option! (&director)
&requireapproval enables server-side room admission approval for a claimed room.
When enabled, guests do not auto-join the room. They are placed in a pending state until the active room director approves or denies them.
This is different from &queue. Queue mode is a guest workflow after the guest has reached the room flow. &requireapproval is a handshake-server admission check tied to the live director claim.
Director link:
https://vdo.ninja/?director=MyRoom&requireapprovalGuest link:
https://vdo.ninja/?room=MyRoomTo show the director a modal popup for each pending request, add &approvepopup:
https://vdo.ninja/?director=MyRoom&requireapproval&approvepopupGuests waiting for approval see a pending/waiting message.
Directors see pending join requests and can approve or deny them.
Pending requests are scoped to the room, not to the director's browser session, so a director reload does not orphan them.
If the director is not present, new guests are not blocked by that director's live approval setting.
If a director claims or reclaims the room, pending guests are re-evaluated against the director's current admission settings.
Matching &roomkey values can bypass manual approval.
&roomcap can be combined with approval to limit the number of admitted and pending guests.
If a guest is transferred into a destination room that also uses &requireapproval, the transferred guest remains pending in the destination room until that destination room's director approves them.
If the pending transferred guest disconnects before approval, they may need to rejoin from the original invite flow.
&requireapproval does not automatically enable sounds or system notifications.
Use &approvepopup for a modal popup. Add ¬ify or &beep for audio alerts.
Last updated
Was this helpful?
Was this helpful?