Create Heimdall-specific zoom accounts and update the meeting script

[kb0rg]

This issue was presented earlier (in Issue #33), but at the time we had a different approach in mind.

However, while working on Issue #46 we came across a couple of other issues with Heimdall-initiated Zoom calls, which prompted us to reconsider this idea.

We should create Heimdall-specific Zoom accounts that will serve as meeting hosts. This will enable us to:

• avoid stepping on thesis employees' accounts
• switch to instant meetings
• have Heimdall start the meeting, then send join url to guests
• allow the meeting to be recorded by setting up automatic recording Note: we could do this with existing users' accounts, but then the resulting cloud recordings would only be accessible to those users

Potential concerns

• We should ensure that users can opt out of recording
• We will need to provide a way to access (delete, download, or share) recordings

History Meetings of type 2 (scheduled) wouldn't resolve to "finished" status, they would revert from "started" to "waiting", so we switched to meeting type 1 (instant) to make watching them easier.

However, those meetings could not be joined unless the host had joined first, so we switched to from posting the "join_url" to the "start_url"

The drawback there was that the first person to join the meeting would appear to be the host (ie, zoom would display the name of the thesis employee whose account was in use, instead of the name of the person who initiated the zoom)

Switching to Heimdall-specific accounts for zoom would allow us to

Related issues that should be addressed or closed when tackling this

28

32

33

[kb0rg]

Seems like folks are getting booted from calls more often lately (or maybe it's just more noticeable now that Heimdall prompts for notes, and people get snarky in response)

We might want to bump this up in priority -- or at least the part referred to in #28