This message was deleted.

Hey @red-father-14173, For moderation, I would recommend checking out the server APIs. • MutePublishedTrack - mutes another participant • UpdateParticipant - set the other user's permission object to include

canPublish

,

canPublishSources

, etc The typical flow we recommend is having your server be in control of who has permissions to perform these operations. And then calling our server APIs to make those changes. We are also in the process of building out an example app to demonstrate participatory livestreaming, where you could have multiple hosts streaming to a large audience. (i.e. Clubhouse with video)

Thank you for taking the time help me out! I've seen the server API and I intend on having the server control the permissions. I'm just not sure how I can use the hooks and components provided to build a custom UI close to the meet example where in each custom

ParticipantTile

it has some buttons like the

ControlBar

that the admin can control the permissions of that individual participant. I'm sure that's doable, I just can't seem to find the right components or hooks to customize the experience.

currently, we don't have built-in components that would do exactly what you want (giving admins control over the situation). However, this should be fairly easy to build yourself. You can start with

ParticipantTile

, but then override the children to provide custom rendering of your own components. Currently, the

ControlBar

is designed to work with a local participant's tracks, however, you could override the buttons so that they are making server API calls to your backend server.