Choose Google busy calendars and review appointment synchronization

Google Calendar has two responsibilities in WeddingBoard: selected calendars block unavailable booking times, and WeddingBoard appointments have copies in the connected account's primary calendar. Existing customer appointment links and mirror identifiers are preserved when reconnecting the same account.

Select busy calendars

The workspace owner opens Calendar → Google preferences. Choose the calendars that should block booking slots. A separate personal calendar can prevent a double booking without becoming the destination for customer appointments. Existing connections may need one reconnect to grant the read-only calendar-list scope. The event permission remains necessary for appointment synchronization.

A selected calendar that returns an error is not treated as free time. Booking availability remains unavailable until it can be verified. Deselect a calendar only when you intend to stop considering its events. Unrelated Google events appear as read-only agenda and availability information; they do not become private WeddingBoard appointment records.

Add a Meet link

Enable Create Google Meet links when the primary calendar advertises Meet support. New copies request a conference with a stable identifier. Google may finish generating its link after event creation; synchronization retrieves the result later. Existing conferences are preserved, and no attendees are added automatically.

The customer sees the current available meeting link on their private booking-management page. The link is hidden after cancellation or disconnection. Keep that management link private, since it also permits reservation changes.

Understand synchronization

WeddingBoard-created appointments synchronize title, start, end, location, notes, and cancellation. Private business notes outside the appointment are not exported. If local and Google edits disagree, open Review calendar versions. Both versions show their time, location, notes, and cancellation state. Choosing a version pins the reviewed local revision and Google snapshot; another edit or connection change requires a fresh review. Remote updates still use Google's revision precondition after approval. A successful provider create with a lost response can be recovered through the appointment's stable Google identifier.

Changes to a client booking or mini-session time must go through Scheduling so reservations and customer notices stay consistent. Conflicting appointments, all-day conversions, and ambiguous daylight-saving times remain held for review.

Times are interpreted in the appointment's saved timezone. Changing the browser timezone does not reinterpret every appointment. A connected-account change is checked again before a provider write, and imported edits cannot replace a newer local revision that appeared during the request.

Reconnect and disconnect

OAuth consent is tied to the initiating owner, workspace, and short-lived request. Replacing the Google account clears old mirror identifiers and generated Meet links while preserving WeddingBoard appointments. New account settings begin with the primary busy calendar and Meet creation off. Disconnect removes local credentials and attempts to revoke the Google token. Existing Google event copies remain in Google.

Google OAuth review, calendar permissions, conference generation, and live-provider conflict behavior are verified together in the final activation phase. See Google's calendar-list permissions and conference creation interface.