Quick start
Use this path when you want to create or join a session as fast as possible.
- Sign in, then open the app hub and choose Start Meeting or Join Meeting.
- Pick LAN/WiFi when everyone is on the same local network, or Remote when participants are joining over the internet.
- Share the room code or meeting link with participants.
- Start screen sharing from the browser prompt once you are inside the room.
Meeting modes
Choose the transport that matches how your group is connecting.
- LAN/WiFi: Best for in-person demos, classrooms, and office sessions where devices share the same network and you want the lowest possible latency.
- Remote: Best for distributed teams, clients, and scheduled internet meetings that need reliable audio, waiting-room controls, and hosted connectivity.
- Both modes let participants join from the browser without installing desktop software.
- If you are unsure, use Remote for any session where participants are not on the same network.
LAN/WiFi room code
Example LAN/WiFi room code: 7 3 9 24 digits
Remote room code
Example Remote room code: K 7 Q 2 M 9 A B8 letters and numbers
Hosting a session
A predictable host flow keeps meetings smooth and reduces join issues.
- Create the room first, then confirm the room code or share link before participants arrive.
- Choose the specific screen, window, or browser tab you want to broadcast instead of sharing your full desktop unless necessary.
- For remote meetings, admit the right participants from the waiting room before starting the main discussion.
- Use shorter room names or a copied link when joining from multiple devices to avoid code-entry mistakes.
Joining a session
Participants can get in quickly when the host shares the right code and mode.
- Open the shared link directly when possible; otherwise enter the room code in the correct LAN/WiFi or Remote flow.
- Allow screen, microphone, or camera permissions only when the meeting actually needs them.
- If a remote host uses admission controls, wait for approval instead of refreshing repeatedly.
- Keep the sender connected during direct file transfers because the file stream comes from the sender device, not from server storage.
Remote-room chat and file sharing
Remote meetings use a hybrid model: service-managed chat delivery plus direct file transfer between participants.
- Remote-room chat messages are delivered live to meeting participants and are not stored in the application database.
- Supported file sharing uses direct participant-to-participant transfer when a peer connection is available and the sender stays connected.
- The browser may keep a local cache of remote-room chat state and shared files during an active meeting so a refresh can recover the room context.
- After a confirmed meeting end, the application schedules that browser cache for deletion after a short post-meeting retention period, with an inactivity-based fallback expiry if that end signal is missed.
Best practices
These habits improve reliability regardless of which meeting mode you choose.
- Use LAN mode for lowest latency during local sessions.
- Keep your browser updated for best performance.
- Share only the window or tab you need during demos.
- For remote meetings, use a stable network connection and avoid closing the sender tab during direct file transfers.
- Review the Privacy Policy if you need the detailed data-handling and retention rules for chat, meetings, or shared files.
Need help with your setup?
Visit support for troubleshooting steps, contact options, and help with login, billing, or meeting access.
Need privacy details?
Review the Privacy Policy for the exact retention and data-handling rules covering remote-room chat, direct file transfers, and browser-local cache behavior.
