w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

Google Calendar: hide a schedule, cancel a booking or retire the link?

Prepare the intended change.

Immutable revision: 19d184e0a7ae2f7287c6e86830056f84186e42f8ff13b01a13f1c5284291b45e. Publication and independent validation are separate; inspect metadata and provenance before use.

Google Calendar: hide a schedule, cancel a booking or retire the link?

For an existing personal primary-calendar schedule on computer; prepare the owner's decision, with actual role and controls unverified.

Choose by the effect

Google's Computer editing guide, schedule visibility documents Booking pages → hover over intended schedule → Options → Hide from calendar. Hiding still allows bookings and leaves booked appointments visible. It is no pause in booking availability.

The Computer cancellation guide, booked appointments and schedule deletion distinguishes:

Intent Documented effect
Cancel one booked appointment Removes it from your calendar, sends a cancellation email and reopens its time on the booking page.
Delete the appointment schedule Removes the schedule and breaks shared booking links; existing bookings remain on both calendars.

The first route is booked appointment → Cancel appointment → Cancel your appointment. The second is appointment schedule → Delete appointment schedule. A forwarded confirmation email lets its recipient cancel the booking; keep that message private. No email receipt or changed plans were observed.

Hand back the selected scope

For different availability, edit the schedule; consult the availability guide [cited revision] separately. Actual slots remain unknown.

Privately identify the exact schedule or booked appointment, intended effect and authority before any later action. Missing role, permission or controls leaves the proposal pending. This excludes third-party appointments, paid bookings/refunds, secondary calendars and co-host settings. No cancellation, deletion, email, account or link-sharing action occurred.

Evidence: Both Google Computer pages read through 2026-10-05T19:05:48.240783Z; no update dates displayed. Sixteen author manual decisions checked; a distinct same-controller checker rechecked those sixteen decisions and six additional boundaries. Shared-controller checks supply no independent review or observed booking outcome. Recheck before use, after changed account/controls/booking state and by 2026-11-05T19:05:48.240783Z. Follow the calendar standard [current article]. Feedback should identify the unclear public step without event details, confirmation messages or private links.

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.