- Home
- Features
- Live classes and scheduling
- Managing Zoom integration and account pooling
- Find out Zoom is broken today, not on the day of the class
Find out Zoom is broken today, not on the day of the class
Every row in the Zoom accounts table has Re-verify in its menu. Choosing it makes ClassTablet mint a token with that account's credentials and read back the granted permissions. When it finishes, the account's status is updated and the result is reported on screen.
How it is done today
If the Zoom client secret is rotated or the app is deactivated, ClassTablet can no longer create links, and that is discovered minutes before a class. The teacher waits, students message asking for the link, and the admin goes hunting for fresh credentials in a hurry.
How it works
- 1
Find the row on the Zoom page
Under Dashboard, Settings, Zoom, find the account you are unsure about. Start with any row whose status column says error or expired.
- 2
Choose Re-verify
Open the three-dot menu at the right of the row and pick Re-verify. While it runs, the screen shows a 'Verifying Zoom account' message.
- 3
Read the result
If everything is in order you get 'Zoom account verified'. If something is wrong, the failure message appears and the status column keeps showing it.
- 4
Fix it if needed
When verification fails, check in Zoom that the app is still activated and the scopes are present, and update the webhook secret token before trying again.
What runs on its own, what stays in your hands
What happens automatically
During the check ClassTablet mints a Zoom token, reads the granted permissions back and updates the account's status on its own.
What you control
When to run the check, and what to change in Zoom, is the institution admin's call.
What it looks like
Who uses it
- Used by:
- platform
- Institution types:
- Coaching centres
- Schools
- Colleges
- Online teaching platforms
Plan availability
- CustomNegotiated
Frequently asked questions
Does verifying disturb a class in progress?
No. Verification only mints a token and reads the permissions back. It creates no meetings and ends none, so a class already running carries on.
How often should we verify?
There is no fixed schedule. Running it after rotating the app's secret, after adding scopes, or when the table shows an error is enough.
If verification fails, do classes stop?
A failure means the credentials no longer work, so creating new links can be blocked. Links already created keep working on Zoom's side.