Use SSO or a signed-in access layer before sending users to VDO.Ninja.
SSO is its own access path. It is separate from VDO.Ninja's room-cap, approval, queue, and source-prompt parameters.
Use SSO when you need identity checked before a person reaches the VDO.Ninja room flow. In that setup, the SSO or invite system handles sign-in, allowlists, identity policy, and access decisions. Approved users are then sent to the intended VDO.Ninja link.
SSO is the better fit when you need:
sign-in before users reach the room
allowlists based on accounts, email domains, groups, or other identity rules
an access layer that is separate from VDO.Ninja room state
a lobby or event flow where people request access before receiving the real invite
SSO is not the same as:
&requireapproval, which is VDO.Ninja room admission approval
&roomcap, which caps admitted guests in a claimed VDO.Ninja room
&approvepopup, which shows the director a modal approval prompt
&prompt, which asks a publisher before sending media to a viewer
&queue, which controls guest activation after a guest reaches the room workflow
Those options can still be useful after SSO sends someone to a VDO.Ninja link, but they are different layers.
One common pattern is:
User opens an event or invite page.
SSO or the invite system checks identity.
Approved users receive or are redirected to the VDO.Ninja room link.
VDO.Ninja room controls, such as &requireapproval or &queue, optionally handle final production workflow.
Another pattern is a self-hosted VDO.Ninja deployment behind an identity gateway, such as Cloudflare Zero Trust. In that case, users sign in before the VDO.Ninja page is served.
For larger lobbies, use app.invite.cam. It is designed around authenticated room ownership, waiting lists, and owner-controlled grant/revoke access.
Last updated
Was this helpful?
Was this helpful?
