How to promote participant that connected to webinar with Web Client SDK to panelist or unmute him?

Description/Error
Dear Staff,
Could help us to find a way to promote participant that connected to webinar with Web Client SDK to panelist and/or unmute him?
We use the way where the host tries to promote participant that connected to webinar with Web Client SDK 1.5.0 to panelist and permanently achieves error that inform us that “we use the old client Zoom version”. Do we have a chance at least unmute him?

Andrey

Hey @andrey.petrenko,

Have you tried the mute(params) function?

Example:

ZoomMtg.mute({
    userId: 16797696,
    mute: false
});

https://marketplace.zoom.us/docs/sdk/native-sdks/Web-Client-SDK/api-reference

Let me know if this helps!

Thanks,
Tommy

Tommy, We us next options:
It’s a webinar were present 2 groups:

  • panellists - use Zoom client SW
  • listeners/participants - use Web SDK HTML5 client
    Listeners/participants - always muted by default as we are talking about “webinar”…
    And the question is - How to unmute the particular Listener/participant?

Andrey

Hey @andrey.petrenko,

We will have an endpoint to make a participant a panelist in early Q4. You can track our release log here.

In the meantime, if you know the userId of the webinar participant who wants to be unmuted, you should be able to call this JS SDK function to unmute the participant:

ZoomMtg.mute({
    userId: 16797696,
    mute: false
});

Let me know if that works!

Thanks,
Tommy

Tommy,
Thank you for your support but you blowed our mind right now :slight_smile:
Are you sure that we can “to unmute listeners” in such way? We suspect that only way to do so is using button by host in the “Zoom client”.
Could you add more details or share a note regarding to this?

Andrey

1 Like

Hey @andrey.petrenko,

You are right, this feature is not available for the JS Web SDK as of now.

It can only be done by the webinar host in the Zoom Client.

We will have an endpoint to make a participant a panelist in early Q4. You can track our release log here.

Thanks,
Tommy