How to enter a Bedrud room from the web app: pre-join preview, connect, basic media controls, and access gates.
Pre-join (welcome shell)
Before media connects you typically see:
- Display name
- Microphone and camera preview
- Device selectors for mic, camera, and speaker (when available)
Set these before joining so the first connection uses the right devices.
Join and connect
- Click Join (or equivalent).
- You should see a short loading shell, then the connected meeting UI — not an infinite spinner.
- Other participants appear as tiles or avatars once they have joined.
If connection fails, check browser permissions, network, and that the server’s LiveKit/WebRTC ports are reachable. Operators: see WebRTC Connectivity.
Basic controls
| Action | Expected behavior |
|---|---|
| Mute / unmute mic | Other participants stop/start hearing you |
| Camera on / off | Your video tile updates for others |
| Leave room | You disconnect cleanly; others should not keep a zombie participant forever |
| Rejoin | Joining the same room again works after leave |
Multiple participants
Use two browsers (or normal + private) to confirm:
- Both sides see each other’s tiles
- Mute and camera state is visible remotely
Gated rooms
Rooms may require a password, wait for approval, or other access checks depending on room settings. Complete the room access dialog when shown, then proceed to pre-join / join.
Guest join (no account) may be allowed on some instances — share a link and guests enter with a display name only. Guest join fails closed if the room is full or capacity tracking fails (no media token). Guests get a stable signed identity cookie (bedrud_guest_id) so room bans stick across revisits. Lobby count for public rooms may be public; participant identity lists require authentication.
After you are in
- Stage Mode
- Chat
- Meeting Controls — screen share, spotlight, moderation
- Audio & Push-to-Talk