Google Calendar private events: what each person with access actually sees

Two settings decide what someone sees

Calendar sharing sets a person’s baseline: Google’s levels are “See only free/busy (hide details)”, “See event details”, “Make changes (see private events as free/busy)”, “Make changes and see event details” and “Make changes and manage sharing”. Event visibility then adjusts that baseline for one event: Default visibility, Public or Private.

Default visibility follows the calendar’s sharing settings, so it changes nothing. The other two override the baseline in opposite directions, which is where surprises happen.

Public widens access for that one event

Google defines Public as: anyone who has access to view your calendar can see all the details of this event, even if your overall calendar is restricted to free/busy. A colleague who normally sees only grey busy blocks will see the title, place and description of that one event.

This is useful for, say, an office-hours slot you want everyone with access to read. It is a poor choice for anything you would not show to every person and group on your sharing list, including organisation-wide or public sharing if you have it.

Private narrows access, but not for everyone

Google says Private hides all details from everyone except you and people with “Make changes and see event details” or higher. So a co-manager with that level still reads your private events in full. Someone with “Make changes (see private events as free/busy)” does not.

Google explicitly describes an additional distinction for the “Make changes (see private events as free/busy)” permission: a private item marked Busy appears as a busy block, while a private item marked Free is hidden from that recipient’s calendar grid. Do not generalise that exact display rule to every other permission level without checking the recipient’s view. Private controls details; Busy or Free separately describes availability.

An invitation and a calendar-sharing grant are separate routes. Private does not recall information already sent in an invitation. Google warns that some details can remain visible when guests or rooms are involved, including the event’s start, end and creator. Check the actual audience rather than treating Private as a confidentiality guarantee.

Worked example: one appointment, four viewers

A fictional manager adds “Contract renewal — Northwind, Room 4” on Thursday at 14:00 and marks it Private and Busy. Their calendar is shared four ways: a team Google Group with free/busy only, a peer with See event details, an assistant with Make changes (see private events as free/busy), and a deputy with Make changes and see event details.

The group, the peer and the restricted editor each see a busy block at 14:00 without the private title; the deputy can read the details. For the restricted editor specifically, Google says changing that private event to Free hides it from their grid. Do not assume all other viewers have the same Free display. If this otherwise non-private event were marked Public, everyone with calendar-view access could read its details.

Recovery check: if a Public event was a mistake, set it back to Default visibility and save, then remember that anyone who already looked may have read it. Changing visibility affects what is shown from now on; it does not recall what was seen.

Change and verify one event

Open the event, choose edit, find the visibility control (shown as Default visibility until changed), pick Default visibility, Public or Private, and save. For tasks, Google says only tasks with a start and end time can have their visibility changed; tasks without times are always private.

To verify without exposing real data, ask a colleague who holds a known permission level to look at a harmless test event you mark Private and Busy, then Public. Do not share your account credentials to “see what they see”. On a work or school account, Google notes your administrator can limit sharing or turn off permission settings, so the levels you see may be fewer.

Recurring events have an important limit: Google documents one visibility setting for the whole series. Trying to change one occurrence or a subset applies the visibility change to the entire series. Use a harmless non-recurring event for the recipient-side test above.