What Privacy and Access Control Options Does a VDO.Ninja Room Offer?

A VDO.Ninja room gives the director three guest-access modes (public, SSO required, or allowlist only), an optional "require director approval before guests can join" gate, and a set of in-room controls that let the director mute guests, disable their cameras, or stop their sharing. The trade-off to understand up front: once someone is in your room and you are acting as director or authenticated remote controller, that role can remotely change their camera, microphone, URL, and digital video effects while their page is open. So access control is really about who you let in, not about limiting what a director can do afterward.

Guest access modes

When you create a room, the setup screen offers these guest access options:

For the allowlist, you enter a comma-separated list using @handle or email patterns such as *@domain.com. The page notes you can change these settings later in Room Settings, so you are not locked into your first choice.

One related detail from the room setup: SSO rooms use a managed room secret, and the manual room password field is disabled in that case. If you want a simple shared password instead, that path is tied to non-SSO rooms.

Approval and in-room controls

Beyond the entry gate, the room creator can enable "Require director approval before guests can join." With this on, a guest sits in a pending state — the interface shows a "Pending Join Requests" area — until the director admits them. This is the closest thing to a manual door: even someone with the link cannot enter until you approve.

Once guests are in, the director has live controls. The page evidence shows states such as:

• "Only the director can hear you currently."
• "The director has muted you."
• "The director has disabled your camera temporarily."

There is also a Data-only mode ("no local camera or mic is being published") and a Stop Sharing control, so a participant can be limited to data rather than live A/V.

The remote-control caveat

This is the part worth reading twice. The camera-to-OBS page carries an explicit privacy warning: "A director or authenticated remote controller will be able to remotely change your camera, microphone, URL, and digital video effects while this page is open, if you continue."

That means joining a room as a guest is not a passive act. If you are not comfortable with someone else being able to switch your camera or mic while your page stays open, close the page when you are done, or don't join rooms run by people you don't trust. VDO.Ninja's own tip list says it plainly: "Invite only guests to the room that you trust."

Practical setup for a private room

1. Create a Room and give it a name.
2. Under guest access, pick Allowlist only (or Require SSO if your guests have accounts) instead of Public.
3. Enter the allowed handles or email patterns, comma-separated.
4. Turn on Require director approval before guests can join if you want a second check at the door.
5. Optionally disable video sharing between guests — the page notes this improves performance and also reduces what guests can see of each other.
6. Share the room link only with the people on your list.

A note on what is not specified

The page evidence describes these controls but does not state retention periods, encryption details, or what happens to recordings. The Recording option is labeled experimental, so treat any recording feature as unverified for sensitive sessions. If your use case depends on those guarantees, confirm them before relying on the room for confidential material.

The short version: use allowlist or SSO plus director approval for anything private, and remember that the director role itself is powerful by design — the strongest privacy control is choosing your guests carefully in the first place.