I’ve found an undesired behavior when hosting a meeting, and I’m not sure if it depends on some setting that can be changed when creating a meeting via API.
Suppose a user creates a meeting, then he joins as host. Other participants join using the non-login join link. If the host leaves the meeting for several reasons (network goes down, application crashes, etc) a random user will become host and be able to mute/kick people out of the meeting or disrupt the meeting in other ways.
Moreover if the original host rejoins the meeting, he’ll not be able to regain his role until the previous connection is kicked out due to timeout.
I think this is a serious problem, in particular if a random user can become host and have rights on other participants.
Can this behavior be avoided with some setting when creating the meeting?