Why Do Secondary Google Calendars Not Block Jane Online Booking?

A secondary or shared Google Calendar does not block Jane online booking because Jane’s documented inbound sync reads only the primary calendar of the connected Google account. Events on that primary calendar appear in Jane as Busy - Google Calendar Event and prevent patients from booking the covered time online. Events on other calendars in the same account do not enter Jane through this connection.

The confusion comes from treating every calendar visible in Google as one availability source. Google can show primary, secondary, shared, and subscribed calendars together. Jane does not evaluate all of them for inbound blocking. Calendar ownership, sync direction, and administrative double booking create separate boundaries.

Why do secondary Google calendars stay invisible to Jane?

Jane states that only the primary calendar for the connected Google account is synced. Events from secondary or shared calendars do not show in Jane. The primary calendar is the first calendar listed under My Calendars in that Google account. Moving between calendars in the Google interface does not change which one Jane reads.

Jane also limits each staff profile to one connected Google account. That means connecting an account with a convenient email address is not enough. Its primary calendar must be the calendar that contains the events intended to block patient booking. A team can otherwise see the event in Google, see a Connected badge in Jane, and still have no corresponding Busy block.

This is a documented coverage boundary, not proof of an intermittent failure. Operational inference: identify the event’s actual calendar before reconnecting accounts or changing shifts. Check which calendar owns it, not merely which account can view or edit it.

Keep that availability diagnosis separate from acquisition attribution. A booking that remains available because a block was absent still has its own operational source. The guide to appointment source versus marketing source explains why calendar ownership should not rewrite campaign or channel data.

What is the difference between Jane’s two calendar directions?

Jane documents two separate one-way flows rather than an automatic two-way sync. The inbound Google Calendar connection brings primary-calendar events into Jane as Busy blocks. The outbound Jane calendar subscription sends appointments or shifts to external calendar software through private iCal URLs. These flows solve different jobs and should not be used as proof of each other.

The outbound subscription is view-only. Jane says it does not change the external calendar to show the user as busy and cannot be edited to manage availability. Subscribing to a Jane feed in Google therefore does not make a secondary Google calendar an inbound blocker. It only lets the staff member view selected Jane schedule information in an external calendar.

Name the direction before testing: “Google primary to Jane” for inbound blocking, or “Jane to external calendar” for outbound visibility. Avoid calling either path “two-way” in runbooks. That label hides which system owns the event and enforces availability.

Calendar movement should not create new demand in reports. If an appointment is changed after booking, use the separate method for preserving original booking source after a reschedule while recording the later action independently.

How should a clinic identify the primary Google calendar?

Jane identifies the primary calendar as the first calendar under My Calendars in the connected Google account. Open the test event and verify its calendar field. A color, shared access, or appearance in the same weekly grid is not enough. The event must belong to that primary calendar for Jane’s documented inbound sync to import it.

If the event belongs to a secondary or shared calendar, choose an operating rule before copying it. The clinic might use each practitioner’s primary calendar, connect another account, or manage the block in Jane. Those are workflow choices. Jane’s cited guides do not prescribe one migration strategy.

Operational inference: do not duplicate a whole shared calendar blindly. Repeated and all-day events may block more time than intended, and copied events can lose their ownership context. Test one non-sensitive event first. Use a neutral title because Jane hides titles from its schedule view, but Google permissions still govern who can see the original event.

How can staff verify that a primary-calendar event arrived?

A synced Google event should appear on the Jane schedule with the label Busy - Google Calendar Event. Jane says the schedule should update after about one minute, though a page refresh may be needed. The inbound window covers events from the past 30 days through 12 months into the future.

Create or select one neutral test event on the primary calendar at a time that is otherwise offered online. Wait for the documented update period, refresh Jane, and confirm the Busy block appears at the same time. Then check the patient-facing booking path with a non-identifying test. Do not use a patient’s existing appointment or private meeting details as test content.

If the Busy block does not appear, capture the connected account, staff profile, event calendar, time zone, creation time, and refresh state. Do not disconnect first. Jane says disconnecting removes previously synced Google events from its schedule, so preserve evidence before changing the connection.

A successful block proves availability behavior for that test. It does not prove reminder ownership or message suppression. Clinics using several systems should separately test duplicate appointment reminder paths after the booking workflow is stable.

Why can staff still book over a Google Busy block?

Jane distinguishes patient online booking from administrative booking. Imported Google events block the covered time for patients online. However, if administrative double booking is enabled in Schedule Settings, staff can still create an appointment at the same time as the Google event. Seeing an internal override does not mean the inbound sync failed.

Test the two paths separately. First, use the online booking experience to confirm the time is unavailable to a patient. Second, inspect the administrative schedule and relevant double-booking setting. Record whether the staff action displayed a warning or allowed the overlap, but do not infer a specific warning behavior that Jane’s cited calendar guide does not document.

Operational inference: clinics that expect a hard internal block should review who may double-book and under which procedure. The cited sources establish that the override can exist, not which staff roles should have it or how a clinic must govern exceptions. That decision belongs to clinic policy and current Jane configuration.

What privacy details matter in Jane calendar subscriptions?

The inbound Google sync shows only Busy blocks in Jane, without the Google event title, description, or guest information. Jane says these events do not appear in reports or exports. This limits what Jane displays, but it does not turn Google Calendar into a suitable place for patient or treatment details.

The outbound iCal subscription has a different privacy concern. Jane notes that appointment notes can contain PHI or other confidential information and lets staff exclude notes through Privacy and Sharing settings. It also warns that Google Calendar subscription defaults may expose details to people who can view the Google calendar unless sharing is configured carefully.

Use neutral synthetic events, keep private calendar URLs confidential, and confirm sharing settings. An iCal URL is an access mechanism, not a public link for tickets or shared documents. Troubleshooting needs timestamps and configuration evidence, not names, contact details, reasons for visits, or clinical notes.

What is a reliable test sequence for this problem?

A reliable test proves calendar ownership, inbound import, patient blocking, and administrative override as separate outcomes. Changing several settings at once makes the result hard to explain. Use one staff profile, one connected account, one neutral event, and one otherwise bookable time.

1. Confirm the Google account shown as Connected in the staff profile.
2. Identify the primary calendar under that account’s My Calendars list.
3. Create a neutral test event on the primary calendar.
4. Wait about one minute, refresh Jane, and find the Busy block.
5. Confirm the time is unavailable through patient online booking.
6. Test administrative booking separately if double booking is enabled.
7. Repeat with a secondary calendar only to demonstrate the documented coverage boundary.

Record each result without creating a real patient record. If a synthetic booking is permitted and necessary, remove it through the clinic’s approved process and preserve its test label. Later reporting should use a stable outcome taxonomy rather than treating a calendar test as a genuine booking. The clinic booking outcome taxonomy provides that separation.

Frequently asked questions

Can Jane sync a shared Google calendar for blocking?

Jane’s guide says secondary and shared calendars do not sync into Jane. Only the primary calendar of the connected Google account creates the documented Busy blocks. Shared access to an event does not make that event part of the primary calendar.

Does subscribing to Jane’s iCal feed create Busy time in Google?

No. Jane describes its calendar subscription as view-only and says it does not change the external calendar to show the user as busy. The iCal feed displays Jane appointments or shifts externally; it is not the inbound Google-to-Jane availability connection.

Why can reception book a time that patients cannot?

Administrative double booking may be enabled in Jane’s Schedule Settings. In that case, a Google event still blocks patient online booking, but staff can book administratively at the same time. Test the patient and staff paths independently before diagnosing a sync failure.

How far does Jane import Google Calendar events?

Jane says the inbound sync brings over all primary-calendar events from the past 30 days through 12 months into the future. An event beyond that window is not a valid test of current coverage. A new event should update after about one minute, though Jane may need a refresh.

References

• Jane App, Google Calendar Sync, reviewed August 16, 2026.
• Jane App, Subscribing to Your Calendar for Staff, reviewed August 16, 2026.