Feature
Use Zoom for manager 1:1s without losing control of who actually hosts the meeting
EvalSuite supports Zoom-backed 1:1 scheduling with a simple hybrid model. Managers can connect their own Zoom Host for personal ownership, and org admins can configure one workspace fallback host so Zoom still works when a manager has not connected a personal account yet.
Why teams care
Schedule manager 1:1s on Zoom with personal host ownership first and one admin-managed workspace fallback when needed.
- Manager-owned Zoom Host accounts take priority for their own meetings
- One admin-owned workspace fallback host can cover managers without a personal host
- Connected Google and Microsoft calendar invites stay aligned with the latest Zoom links
Keep the real host tied to the right person first
When a manager connects a personal Zoom Host, EvalSuite uses that host for their scheduled Zoom 1:1s. That keeps meeting ownership and host controls anchored to the manager who is actually running the conversation.
If the manager has not connected a personal host, EvalSuite can fall back to one admin-managed workspace host instead of forcing every manager to connect Zoom on day one.
Keep the shared fallback simple and predictable
The workspace fallback model is intentionally narrow: one admin-owned Zoom Host per workspace, used only when the manager does not have a personal host connection.
- Org admins choose the fallback host from active admin Zoom connections
- Personal manager hosts still win whenever they are available
- Overlapping fallback-host Zoom meetings are blocked instead of silently colliding
Keep invite updates in one workflow
When a scheduled 1:1 uses Zoom, EvalSuite stores the current Zoom join and host links on the meeting record and pushes those updates into connected Google or Microsoft calendar invites when available.
That keeps managers from manually editing invites every time a meeting moves or the provider changes.
Make Zoom a clean part of your 1:1 workflow
Start with the EvalSuite room, add personal Zoom Hosts where needed, and use one workspace fallback host when your team wants a lighter setup path.