Skip to main content

Overview

Sub-meetings split one main meeting into several sub-meetings (groups). Members assigned to a group enter their own meeting, and return to the main meeting when the discussion ends.
  • The main meeting must be created in MeetingMode.subMeeting mode
  • The group orchestration APIs all have the admin prefix and are called by the host / a co-host
  • Group information is represented by SubMeetingInfo; mainMeetingId points to the main meeting, and meetingId is the group’s own meeting ID

Orchestrate groups

In each SubMeetingInfo returned by adminSubMeetingList, users are the assigned members, and status is the group’s meeting status (MeetingStatus).

Start and stop

After receiving the corresponding event, the member side switches meetings on its own:
Switching meetings requires “exit the current meeting first, then enter the target meeting.” The SDK doesn’t switch for you automatically—when to switch and what to show the user during the switch are up to your app.

Move members between groups

The moved member receives:
Likewise, your app needs to exit the old meeting and enter the new one itself.

Groups ask the host for help

Members in a group can ask the main meeting for help:
If the host has enabled the out-of-meeting message path, they receive:
This notification goes through the out-of-meeting message path, so you must call enableIm() first; see Out-of-meeting messages.