LiveKit provides several ways to use metadata for synchronizing and storing application-specific data across rooms and participants: • Participant Metadata: Each participant has a

metadata

string field (usually JSON). You can set or update this using SDK methods such as

await localParticipant.setMetadata(metadata)

in JavaScript. This is ideal for passing information like user profiles, roles, or interaction states. You need the

canUpdateOwnMetadata

permission to update this field. • Participant Attributes: Attributes are key-value string pairs, allowing you to update specific information independently, e.g.,

await localParticipant.setAttributes(attributes)

. • Room Metadata: The room also has a metadata field, which is settable only via server APIs during creation or with admin privileges. This can be used for application-scoped settings such as livestream configuration or global features for all participants. Common use cases include user profiles, hand-raising features, SIP metadata, and application-level room configuration. Metadata and attributes are visible to all participants and synchronize automatically, but are not intended for very frequent updates. For more details or examples in a specific programming language or use case, let me know what you’d like to see. References available upon request. Sources: Room metadata | LiveKit Docs | Job lifecycle | LiveKit Docs | src/room/participant/LocalParticipant.ts | SIP dispatch rule | LiveKit Docs | Runtime/Scripts/Participant.cs | livekit-rtc/livekit/rtc/participant.py | lib/src/participant/local.dart | Shared/Types/RoomMetadata.swift | sample-livestream/src/main/java/io/livekit/android/sample/livestream/room/s... | Participant attributes and metadata | LiveKit Docs