For the complete documentation index, see llms.txt. This page is also available as Markdown.

app.invite.cam

A larger lobby and invite workflow for controlling access before users join VDO.Ninja.

https://app.invite.cam is a lobby and invite workflow that can sit in front of VDO.Ninja.

Use it when you expect many people to request access, or when you want authenticated room ownership, waiting lists, and owner-controlled grant/revoke decisions before sending people into the actual VDO.Ninja room.

What it is for

app.invite.cam is useful for:

  • larger public lobbies

  • events where many people may request access

  • owner-managed waiting lists

  • signed-in or authenticated access workflows

  • reusable host room links tied to a signed-in owner

  • separating the public invite/lobby from the final VDO.Ninja room link

Permanent room idea

The simple version: the host signs in, gets a room under their name, and shares that app.invite.cam room link. Guests can wait in the lobby, raise their hand, chat, or be moved into the live VDO.Ninja room when the host is ready.

This is different from a raw VDO.Ninja &push stream ID. app.invite.cam manages the lobby, identity, helpers, and invite rules before someone reaches the final VDO.Ninja room flow. If your only problem is "my OBS browser source changes when a guest refreshes," start with Permanent links, reusable invites, and stream IDs.

How it differs from VDO.Ninja URL parameters

app.invite.cam is not the same layer as VDO.Ninja room/source parameters.

  • &requireapproval approves guests at the VDO.Ninja handshake-server room-admission layer.

  • &roomcap caps admission to a claimed VDO.Ninja room.

  • &queue controls the guest activation workflow inside VDO.Ninja.

  • &prompt asks a source publisher before sending media to a viewer.

  • app.invite.cam handles the larger invite/lobby and owner grant/revoke workflow before the final VDO.Ninja room flow.

Typical flow

  1. A user opens the app.invite.cam lobby link.

  2. The user signs in or joins the lobby flow.

  3. The room owner sees the waiting user.

  4. The owner grants or revokes access.

  5. Approved users are sent to the intended VDO.Ninja link or room flow.

How to selectively allow accessSSO and signed-in accessHow to get permanent linksInvite Link Generators

Last updated

Was this helpful?