Join & room UX

What end users experience after your LMS or API issues a join link.

Flow

1. Integrator calls wire API join (with fullName, optional avatarURL / userID / logoutURL) or uses JSON join URLs
2. API validates password/role and issues a short-lived ticket
3. Browser redirects to https://meet.{domain}/join/{ticket}
4. User enters the 2meet meeting room (video, whiteboard, chat, recording)
5. On leave/end, if logoutURL was set, the browser returns to the LMS

Display name & avatar

Pass fullName and optionally avatarURL on wire join (BBB-compatible). The avatar appears on video tiles (when camera is off), the participants sidebar, and chat. Invalid or non-HTTP(S) avatar URLs are ignored. Optional userID stabilizes identity across reconnects.

Return to LMS

Pass BBB-compatible logoutURL on create and/or join (join wins). JSON API uses logout_url. After leave or session end, 2meet redirects the browser to that URL so teachers and students land back in Moodle/Canvas (or your LMS).

Organization / class logo

Pass a logo URL on create — JSON org.logo_url or wire meta_org_logo_url — plus optional org_display_name. 2meet snapshots it into meeting metadata so the live header on meet.* shows your school mark. If omitted, desktop shows a centered 2Meet wordmark. Older meetings without a snapshot fall back to live tenant branding.

Native 2meet room

Participants use the 2meet meeting room. Your LMS integration uses the standard wire protocol; the in-room product is 2meet.

Roles

Recordings

When record=true on create, recordings appear via getRecordings with playback URLs suitable for LMS embedding or download.

Session cover (optional)

Optional stage image when the host camera is off or before start. For LMS, pass a URL on create — JSON cover_url or wire meta_cover_url. Separate from live file-share. If omitted, participants see the normal avatar / waiting state. Details: JSON create — cover_url.