Skip to main content
The JitsiParticipant class represents a participant (member) in a conference, containing information about their identity, role, tracks, and custom properties.

Overview

JitsiParticipant provides:
  • Participant identity and metadata
  • Role management (moderator, participant)
  • Track management (audio/video tracks)
  • Custom properties for extensibility
  • Feature capabilities
  • Source information for tracks

Participant Structure

From JitsiParticipant.ts:18-50:

Constructor

From JitsiParticipant.ts:69-110:
The participant ID (_id) is extracted from the resource part of the JID using Strophe.getResourceFromJid(). This is an 8-character hexadecimal string used as the endpoint ID.

Getting Participants

Participants are managed through the conference:

Participant Identity

Basic Information

From JitsiParticipant.ts:182-253:

XMPP Identity

The identity object contains JWT context claims:
From JitsiParticipant.ts:207-210:

Connection Information

Participant Role

Participants can be moderators or regular participants:
From JitsiParticipant.ts:227-231 and JitsiParticipant.ts:309-312:

Participant Tracks

Getting Tracks

From JitsiParticipant.ts:256-270:

Mute State

Check if participant is muted:
From JitsiParticipant.ts:121-126 and JitsiParticipant.ts:284-287:

Track Sources

Participants can have multiple sources (tracks) of the same media type: From JitsiParticipant.ts:10-13 and JitsiParticipant.ts:98-109:
Source information is updated through the signaling layer when participants add, remove, or modify their tracks. The PARTICIPANT_SOURCE_UPDATED event fires when sources change.

Custom Properties

Participants can have custom properties for application-specific data:
From JitsiParticipant.ts:221-224 and JitsiParticipant.ts:398-410:
Common properties:
  • region - Participant’s geographic region
  • codecList - Supported codec list
  • features - Supported feature set
  • Application-specific custom properties

Features

Participants advertise supported features:
From JitsiParticipant.ts:188-193 and JitsiParticipant.ts:273-280:

Participant States

Hidden Participants

Some participants may be hidden (e.g., recording bots):
From JitsiParticipant.ts:290-305:

Silent Status

Participants who joined without audio:

Replacement Status

For participant replacement scenarios:
From JitsiParticipant.ts:314-328:

Participant Events

Participant-related events are fired on the conference:

Practical Examples

Display Participant List

Show Participant Tracks

Monitor Moderator Status

Track Custom Properties

Best Practices

Participants may leave and rejoin. Always get fresh references:
Always handle participant lifecycle events:
Leverage custom properties for application state:

JitsiConference

Learn about conference participant management

Media Tracks

Understand participant track management