# V1.2.0: Improved role management: Original host

**URL:** <https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768>\
**Category:** Web\
**Created:** [April 19, 2022, 3:22pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768 "2022-04-19T15:22:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![efron.vit](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/efron.vit/32/33711_2.png) [@efron.vit](https://devforum.zoom.us/u/efron.vit)\
**Post date:** [April 19, 2022, 3:22pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/1 "2022-04-19T15:22:47Z")

</div>

Hi  
In release v1.2.0, you have had the following update added:

> The user who created a session is considered the “original host”. The original host has the following privileges: the session ends after a configurable timeout after the original host leaves a session, if a new host was not assigned. When the original host rejoins the same session later, if nobody was assigned as the new host by the original host before they left the session, the original host can claim the ‘host’ role, based on its user\_identity setting in the JWT payload. The original host can take the host role at any time from the current host. See user\_identity and role\_type in [Authentication](https://marketplace.zoom.us/docs/sdk/video/auth) for details.

But I noticed that this only works if participants come to a meeting where there is no host (none of them is given the host role, that’s right). But if there is a host at the meeting (with role\_type “1” in jwt-token) and he exits, then the role is still transferred to the participant whose jwt token has role\_type “0”. I also tried to additionally specify user\_identity when receiving the token, but this does not change the situation. The role of the host is still transferred to the participants if the main host leave.

![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/0/7/07378e4613cfedf2adeb755cf68dba1a12514c5b.png)

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [April 23, 2022, 6:34am UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/2 "2022-04-23T06:34:40Z")

</div>

Hey @efron.vit

Thanks for your feedback.

The `role_type` option in JWT is used as the identification of the original host, we will support `reclaimHost` feature based on the original host in the future.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![efron.vit](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/efron.vit/32/33711_2.png) [@efron.vit](https://devforum.zoom.us/u/efron.vit)\
**Post date:** [April 29, 2022, 12:47pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/3 "2022-04-29T12:47:45Z")

</div>

Hi !  
I noticed a bug that if you specify `role_type = 1` when receiving the signature, and if the host exits the conference, then all participants receive a event `'user-updated'`, with the parameter `muted: false`. All participants turn on the microphone =D

![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/8/78d8389e55f85e0304b9be2e5c057c978bacae4e.jpeg)

When I removed the role\_type, the bug disappeared

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [May 29, 2022, 10:48pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/4 "2022-05-29T22:48:41Z")

</div>

Closed on May 29, 2022, 10:48pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 1, 2022, 7:10pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/5 "2022-08-01T19:10:01Z")

</div>

Hey @efron.vit ,

Can I clarify a few things? When you see the `muted: false` property, which event listener are you using? When logging `user-updated` I see this JSON which does not include a muted property:

![Screen Shot 2022-08-01 at 1.06.18 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/f/7f3d2343bf129418af5f1faa3f9c392a624f2232.png)

That being said, when calling `client.getAllUser()` after the `user-updated` event is triggered, I do see `muted: false` when the user **has not joined audio** (have not called `stream.startAudio()`) which would be inaccurate, but if the user has joined audio (have called `stream.startAudio()`) and is muted, I see `muted: true`.

When you saw this functionality, was your user connected to audio via `stream.startAudio()`.

I tested with version 1.4.0.

CC @vic.yang

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 1, 2022, 7:10pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/6 "2022-08-01T19:10:08Z")

</div>

Opened on August 1, 2022, 7:10pm UTC



---

<div class="post-metadata">

**Author:** ![efron.vit](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/efron.vit/32/33711_2.png) [@efron.vit](https://devforum.zoom.us/u/efron.vit)\
**Post date:** [August 18, 2022, 1:12pm UTC](https://devforum.zoom.us/t/v1-2-0-improved-role-management-original-host/67768/7 "2022-08-18T13:12:37Z")

</div>

> [@tommy](#):
>
> That being said, when calling `client.getAllUser()` after the `user-updated` event

I did the same thing, but I meant exiting the conference, not entering (it was version 1.2.0)

Thanks, I’ll check on the new version.

* * *

Good, now it works as needed
