Connection scope
A calendar connection belongs to the workspace and is associated with the approved location or professional. The account chooses read/write or supported sync direction, and the provider permissions must match the intended behavior.
Availability protection
- Active external events remove time from server-side availability.
- A shared calendar can provide team-level busy time while professional rules still control eligibility.
- Individual calendar mode lets each professional maintain a separate connection and schedule.
- Provider changes after a slot was offered cause the booking recheck to fail safely if the interval is no longer available.
- Sync errors remain visible and do not silently count as current data.
Connection is not the same as readiness
An OAuth connection can succeed while permissions, calendar selection, webhook/watch state, or initial sync remains incomplete. Scheduling becomes authoritative only after the required provider and NevoDesk health checks pass.
✓
Source-of-truth policy
This article is part of the same maintained knowledge corpus used by NevoGuide. Live provider evidence and saved workspace configuration remain authoritative for your account’s current operational state.