Member Junction
    Preparing search index...

    One participant on the meeting roster as the Meeting Controls channel consumes it. Minimal and platform-agnostic — a bridge driver maps its native roster (import('./media-tracks').BridgeParticipantInfo, a Zoom participant, a Twilio call leg, …) onto this shape when feeding the channel's event source.

    Structurally identical to @memberjunction/ai-agents's MeetingParticipant, so an event source implemented here satisfies the channel's injected dependency.

    interface BridgeMeetingParticipant {
        DisplayName?: string;
        IsAgent: boolean;
        ParticipantId: string;
        Role: BridgeMeetingParticipantRole;
    }
    Index

    Properties

    DisplayName?: string

    Human-readable display name, when the platform reports one.

    IsAgent: boolean

    Whether this participant is an agent bot (the facilitator excludes agents from hand-raise / call-on).

    ParticipantId: string

    Stable platform-native participant id (the key the queue / speaking / mute state is keyed on).

    The participant's role in the meeting.