Nobody should type in forty Zoom accounts by hand
Zoom accounts can be set up from a spreadsheet. Once the file is given and its columns are matched up, the rows are verified against Zoom one after another, and what happened to each row is listed at the end.
How it is done today
A large coaching centre keeps a separate Zoom account for each teacher. Entering them one at a time means copying long client ids and secrets by hand, which goes wrong, and forty accounts eats half a day.
How it works
- 1
Provide the file
Give the file holding the Zoom account details. Each row is one account, along with which teacher that account should be assigned to.
- 2
Match up the columns
Say which column in the file holds which detail, so the label, the account id and the secrets all land in the right places.
- 3
Review, then run it
The rows can be looked over before anything happens. The run then verifies them against Zoom one at a time rather than all at once.
- 4
Look at what did not go through
Any row that could not be set up carries the reason it failed, and by then the rest of the rows are already in place.
What it looks like
Who uses it
- Used by:
- Admins
- Institution types:
- Coaching centres
- Schools
- Colleges
- Online teaching platforms
Plan availability
- CustomNegotiated
Frequently asked questions
Does one bad row cancel the whole import?
No. The row that failed is set aside with its reason and the rest carry on, so accounts already verified against Zoom are not thrown away.
Why are the rows not sent all at once?
Each row costs a fresh authorisation with Zoom and a lookup of its users. Sending forty together just gets the requests throttled, for no gain in speed.
What if the account registers but the host does not?
The account is registered and verified, and only the host could not be chosen, so that row is set aside for the admin to finish by hand.