Issues with new Zoom -> meet.churchofjesuschrist.org

[simph1]

Example of why a Host Code is better:

The administrator (person who only has the zoom credentials) (limiting access to credentials is essential)

1. Sets up the meetings, rooms etc.

2. The host will be given the host code

Day of the meeting

1. The host who has no credentials clicks on the link to the broadcast meeting and signs into the zoom app or on desktop

2. The host signs in as a free account

3. The host clicks on the participants and then his or her name

4. The host clicks on "take host" and types in the host code

5. The host is now moderator and has full access to all settings as if they had the credentials

6. The host cannot sign into zoom.us

7. The host cannot change the account settings and mess things up for other meetings and other hosts

After the meeting

1. The administrator changes the code

2. The host cannot now become the host to any future meetings or change settings in zoom

What if the host messes around in the meeting?

1. The administrator will sign in as the host with the credentials

2. The host is instantly a normal user and kicked from being a host instantly

3. The administrator gives someone else the host then leaves the meeting

I hope this helps

Simon

[Wattsuk]

Ah, I can see why you would operate it that way.

In our stake we have an admin who logs into every meeting and can then assign hosts/co-hosts as needed for that meeting. No need for the host key but an admin has to make sure they're in the meeting, even if it's just for 2 minutes at the start to get the appropriate hosts assigned.

[simph1]

That again is why the host code is useful.

You give the code to the host, and the meeting is setup months in advance...

The assigned host with the host code would then gain access to the zoom meeting as host with that code.

Cool huh?

Simon

[simph1]

If then you have co-hosts, that host would then give out appropriate access to those pre-chosen to be co-hosts.

It saves hassle, time and effort, especially if the admin is sick, lost his or her internet, on holiday, etc...

Simon

[Wattsuk]

It's all well and good as long as your prospective hosts are well trained and understand the process of using the host key.

My memory is foggy about why we stopped trying to use host keys but I believe it was the local leaders who were failing to get to grips with it and then panicking that they couldn't access/start the meeting , then requiring an admin to attend at the last minute to get them sorted out.

Technology is great until it's not.

[russellhltn]

ONLY the STS can get access to meet.churchofjesuschrist.org and it can take up to 2 business days for you to be manually added into the system.

This is true for the section for Zoom licensees. Others can log into meet.churchofjesuschrist.org, but can't see the "Local Units" option, just the "Manage Events" option.

[simph1]

That is why you have training, and also create a PDF or FAQ on a site to answer all their questions.

Then you email the host code to them or text message it, etc.. how hard is it honestly to click participants -> your name -> take host?

Hope this helps... and I agree that technology is great until it's not! lol

Simon

[simph1]

ONLY the STS can get access to meet.churchofjesuschrist.org and it can take up to 2 business days for you to be manually added into the system.

This is true for the section for Zoom licensees. Others can log into meet.churchofjesuschrist.org, but can't see the "Local Units" option, just the "Manage Events" option.

Correct. Also as a side note... if your calling is like mine "Stake Technology Specialist - Website Developer" you won't get access to the website either, that is why they recently renamed my calling to the normal Stake Technology Specialist so that I could advise them and help them wherever necessary.



Simon

[russellhltn]

Also as a side note... if your calling is like mine "Stake Technology Specialist - Website Developer" you won't get access to the website either, that is why they recently renamed my calling to the normal Stake Technology Specialist so that I could advise them and help them wherever necessary.

I don't think there is any such standard calling as "Stake Technology Specialist - Website Developer". Custom callings never get access. Only Standard positions.

[simph1]

Also as a side note... if your calling is like mine "Stake Technology Specialist - Website Developer" you won't get access to the website either, that is why they recently renamed my calling to the normal Stake Technology Specialist so that I could advise them and help them wherever necessary.

I don't think there is any such standard calling as "Stake Technology Specialist - Website Developer". Custom callings never get access. Only Standard positions.

Which is why I stated "why they recently renamed my calling to the normal Stake Technology Specialist"...

Simon