Audit a Google Calendar before sharing it with a new colleague

Calendar sharing seems simple until a calendar is already visible to an organization or the public. Google says broader permissions take priority: if a calendar is public with event details, giving one person only free/busy access does not hide those details from them. Before inviting a colleague, inspect the general audience, named people, and event-level exceptions. The useful outcome is that the colleague can schedule with you without receiving more information or editing power than the job requires.

Before you start​

Work in Google Calendar on a computer; mobile apps do not expose all calendar-sharing controls. Identify which calendar holds the events, since personal, team and imported calendars can look similar in the grid. If it is managed by a workplace, check whether an administrator has set a wider default or restricted changes.

Do it step by step​

1. In Settings for my calendars, choose the exact calendar. Inspect Access permissions for events before adding a person. Record whether it is public or shared across your organization and whether that broad group sees free/busy or full details.
2. Open Share with specific people or groups. Remove stale entries and examine every existing permission. See only free/busy is usually sufficient for scheduling; See event details reveals names, locations and descriptions; editing and manage-sharing permissions have wider consequences.
3. If the calendar is public with details, first decide whether that publicity is still needed. Turn public sharing off or reduce it to free/busy if appropriate, then wait for the change to propagate. Google notes public-sharing changes can take up to four hours.
4. Add the colleague's verified Google Account or approved group with the least access required. Double-check the address before saving. A group can later gain members, so use it only if its membership is governed appropriately.
5. Review several representative events, including a sensitive appointment and a normal meeting. Check their visibility settings and descriptions. A private label may not override every broad permission in the way you expect, so consult Google's access table and test the result.
6. Use a controlled colleague or secondary account to view the calendar as a recipient. Confirm the actual title and detail visibility, then adjust the exact permission if it is too broad. Record the sharing decision for later offboarding.

Check the result​

The named colleague sees only the intended availability or event details; no unintended public or organization-level permission defeats that restriction. The calendar owner knows who can edit events and who can manage sharing.

If something goes wrong​

If a setting is missing, the Workspace administrator may govern it. If the recipient sees more than the named permission suggests, inspect public and organization access first because the broader permission can win. Cached views may take time to reflect a changed public permission; retest later rather than sending sensitive details during uncertainty.

Know the limit​

Sharing permissions apply to the calendar and to events within its scope. A recipient can copy information they were permitted to see, and a publicly visible calendar can be indexed or subscribed to. Permission cleanup cannot recall details already exported or screenshotted. Google Calendar sharing permissions Google public-calendar behavior