Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI Companion2024-07-08 07:55 AM
We are a 7-night-a-week 12-step meeting. Now that we are public, we are having issues with "bombing." Because we have a different leader every night and the person with the account (me) isn't always at the meeting, how do we allow multiple hosts to manage participants, etc.?
2024-07-08 10:41 AM
Welcome to the Zoom Community, @teamsheltie.
This is a difficult situation: How to control access to a meeting but let a different person control the meeting every night. I’m going to ramble through a few things to explain why, before suggesting a few possible solutions.
In your case, as with many others like this, the following circumstances work against you:
There are two approaches that work only for Licensed users on one organizational account: Scheduling Privilege and Alt Host. For any situation where the majority of potential hosts are on the same account, these are well advised.
For your situation, however, only the Host Key approach is helpful. Here are the steps for using Host Key:
This probably looks long and complicated, but the steps are short and simple.
See this Zoom Support article for details on the Host Key:
https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0067063
2024-07-08 11:14 AM
Thanks for this, Ray. We have implemented the 15-minute window, and if the group agrees, we'll do the waiting room. We have also looked at the host key option, and I think it's definitely the way to go. I really appreciate your thorough response!