This message was deleted.

Are rooms specific to a number of participants? Or rooms can all have different number of participants when "locked"?

initially the room starts out with ~2-8 participants, but when it gets into that “lock state”, it becomes just 2 participants. the rest are “kicked” (initially via a friendly data message to the client, but also enforced with a RemoveParticipant) if it’s possible to change the max_participants after room creation, that would definitely work for us! I like the idea of using room metadata but initially wrote it off because there weren’t webhooks for metadata updates and no GetRoom function. but just now reviewing the docs I see ListRooms allows me to pass an array of IDs, so I think that could work as well. we’ll also definitely do short expiry time on the tokens… kind of a no brainer with the refresh mechanism already built-in

So right, you can update the room metadata with

updateroommetadata

(https://docs.livekit.io/server/room-management/#updateroommetadata) and that's correct,

ListRooms

allows you to fetch a specific room if you pass it its ID. As for updating the max_participants once the room has been created, I don't think that's possible. One of the LiveKit Team member could probably confirm this.

awesome, thanks Pat! much appreciated. looking at the code I think it’s immutable but could be mistaken, I’m a go newbie I saw setTrackSubscriptionPermissions mentioned in a thread above and think that may be the path to success here. need to do some testing, but if I can get the 2 clients to make their tracks only subscribable by each other, it sort of becomes irrelevant who else is in the room