Who Can See a Meeting? Calendars, Activities and Private Events

Module 6 of 8 in the chapter Files, Folders, Reports and Other Data, chapter 12 of Securing Salesforce: Sharing and Visibility. Each module stands on its own.

The question this module answers: A coworker saw the details of a meeting they weren’t in. How?

An event in Salesforce is two things at once. It’s an activity: a record, usually related to an account, a contact or an opportunity. And it’s a box on someone’s calendar. Each of those has its own lock. So there are two ways to see a meeting: through the record it’s related to, and through the calendar it sits on.

In chapter 5 I called calendar sharing the smallest way on the map, way 12, and the one people forget. This module is the rest of it.

Through the record: the activity default

Activities, which means events and tasks, have an org-wide default of their own, with two choices (Organization-Wide Default Access Settings (opens in a new tab), Salesforce Help, checked 2026-11-07):

Private. “Only the activity owner, and users above the activity owner in the role hierarchy, can edit and delete the activity; users with read access to the record to which the activity is associated can view and report on the activity.”
Controlled by Parent. “A user can perform an action (such as view, edit, transfer, and delete) on an activity based on whether he or she can perform that same action on the records associated with the activity.”

Read the first one slowly. Private doesn’t mean only the owner sees it. It means only the owner, and the hierarchy above, can change it. Anyone who can read the account can read the meeting logged against it. The out-of-the-box value is Private (Default Organization-Wide Access Levels (opens in a new tab), Salesforce Help, checked 2026-11-07).

So the first answer to the question at the top: the coworker could read the account. The meeting came with it. That’s the sharing model you built in chapters 6 to 11, doing its job.

Through the calendar: the calendar default

The second door is the calendar itself. It has its own org-wide default, and its own levels (Organization-Wide Default Access Settings (opens in a new tab)):

Hide Details: others “can see whether the user is available at given times, but can’t see any other information about the nature of events.”
Hide Details and Add Events: the same, and “users can insert events in other users’ calendars.”
Show Details: “Users can see detailed information about events in other users’ calendars.”
Show Details and Add Events: the same, and they can insert events.
Full Access: they can see details, insert events, “and edit existing events in other users’ calendars.”

The out-of-the-box value is Hide Details and Add Events (Default Organization-Wide Access Levels). So by default, a coworker sees that you’re busy from two to three, not why, and can put a meeting on your calendar. And one thing no setting stops: “Regardless of the organization-wide defaults that have been set for calendars, all users can invite all other users to events” (Organization-Wide Default Access Settings).

Click to enlarge

Each user opens their own calendar

Here’s the part that’s different from every other cabinet in this chapter. The admin sets the floor. The user opens the rest. “Salesforce admins can set organization-wide calendar sharing levels to control how much access coworkers have to each others’ calendars. Admins can’t give coworkers access to event details.” The user can, from the Calendar tab, one coworker at a time, at Hide Details, Hide Details and Add Events, Show Details, or Show Details and Add Events (Share Your Calendar in Lightning Experience (opens in a new tab), Salesforce Help, checked 2026-11-07).

So the second answer to the question at the top: the meeting’s owner shared their calendar with Show Details, maybe years ago, maybe with an assistant who’s since moved teams. Click Who Has Access on the calendar to see who has it, and at what level (same page).

The Private checkbox, and what it doesn’t hide

An event has a Private checkbox. Here’s exactly what it does: it “Indicates whether users other than the event owner can see the event details when viewing the event owner’s calendar” (Event Fields in Lightning Experience (opens in a new tab), Salesforce Help, checked 2026-11-07).

That’s a lock on the calendar door only. The same field description lists what it doesn’t stop:

The override permissions. “Users with the ‘View All Data’ or ‘Modify All Data’ permission see private event details in reports and searches or when viewing other users’ calendars.”
Exports. “Exported data files always contain private events.”
Some events can’t be private at all. “Events with invitees and events being added or changed in another user’s calendar can’t be marked private.”
A private event stands alone. “Private events can’t be related to other records.”

That last one closes the record door: a private event isn’t related to an account, so nobody reaches it through the account. That’s why it works. And that’s also its cost: a private meeting isn’t part of the account’s history.

Test knowledge. Know the two activity defaults, Private and Controlled by Parent, and that Private still lets anyone who can read the related record read the activity. Know the calendar levels, Hide Details, Hide Details and Add Events, Show Details, Show Details and Add Events, and Full Access, and that the default is Hide Details and Add Events. Know that admins can’t give coworkers access to event details; only the user can. Know that a private event is hidden on the calendar, but not from View All Data or Modify All Data, and can’t be related to a record. A likely area, not a known question.

What an architect decides here

The activity default: Private or Controlled by Parent, and whether people understand that Private still means readable through the record.
The calendar default, knowing it’s the floor and each user can open their own calendar further.
When to tell users to check Who Has Access on their calendars, for example when a role changes.
Whether sensitive meetings use the Private checkbox, knowing they then can’t be related to a record, and that View All Data, Modify All Data and exports still see them.
Who holds View All Data and Modify All Data, again, because every private event is open to them.

Beyond the exam: what AI changes. “What’s on my calendar this week?” and “What did we discuss with this customer?” are two of the first questions people ask an assistant. The first reads calendars; the second reads activities through the record. Each one is answered with its user’s access. An agent’s user with Show Details on a dozen calendars can summarize a dozen people’s weeks, and an agent with View All Data sees every private event. Chapter 20 covers agents.

Explore

Organization-Wide Default Access Settings (opens in a new tab), Salesforce Help (checked 2026-11-07)
Default Organization-Wide Access Levels (opens in a new tab), Salesforce Help (checked 2026-11-07)
Share Your Calendar in Lightning Experience (opens in a new tab), Salesforce Help (checked 2026-11-07)
Event Fields in Lightning Experience (opens in a new tab), Salesforce Help (checked 2026-11-07)