Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryCCalendar
Core CRMBeginner

Calendar

The Calendar in Salesforce is the personal and shared scheduling surface that displays Event records (and any Object-Based Calendar built from other records with date fields) in day, week, and month views.

§ 01

Definition

The Calendar in Salesforce is the personal and shared scheduling surface that displays Event records (and any Object-Based Calendar built from other records with date fields) in day, week, and month views. It sits inside the Salesforce Lightning UI as the Calendar tab and as the Calendar component on Lightning pages. Users see their own Events plus any other calendars they have been granted access to. Object-Based Calendars let admins surface records like Opportunity Close Dates, Service Appointments, or custom-object due dates as calendar entries, so the calendar becomes the scheduling overlay across the org's data.

Salesforce Calendar matters because schedule data lives in many places and users need one view. Without the Calendar tab, sales reps would track meetings in Outlook, account close dates in spreadsheets, and field appointments in a separate system. With it, all of those (when surfaced through Object-Based Calendars and Einstein Activity Capture sync) appear in one weekly view. Calendars are also the foundation for Salesforce Scheduler, Field Service appointment booking, and any workflow that needs to consider time availability. The personal Calendar is the entry point; the shared and object-based calendars layered on top are how it becomes operational.

§ 02

How the Salesforce Calendar surfaces work

Personal Calendar and Event records

Each user has a personal calendar showing their own Event records. Events are standard Salesforce objects with Subject, Start Date/Time, End Date/Time, Location, related Account/Contact/Opportunity, and Reminder. Creating an Event from the Calendar drops it on the calendar and on the related record's Activity timeline.

Object-Based Calendars

Admins can build Object-Based Calendars from any object with a date or date/time field. The calendar shows records (Opportunities by Close Date, Service Appointments by Start Time, custom-object due dates) as calendar entries. Users layer these calendars on top of their personal Events for a unified view.

Shared calendars and visibility

Users can share their calendar with specific colleagues or with a public group. Recipients see the shared calendar layered on their own. Sharing happens at the personal-settings level; admins can also set org-wide sharing defaults for events.

Einstein Activity Capture and external sync

Einstein Activity Capture (EAC) syncs Outlook and Google calendars with Salesforce events so users see external meetings inside the Salesforce calendar. The sync is bidirectional with caveats; EAC documentation covers the details. Without sync, the Salesforce calendar shows only Events created in Salesforce.

Salesforce Scheduler integration

Salesforce Scheduler (the appointment booking product) uses the Calendar surface to display Service Appointment records. Bankers, advisors, and field technicians see their bookings in their personal calendar with the same UI as other Events. The integration is transparent to the user.

Calendar in mobile experience

The Salesforce Mobile App renders the calendar in a touch-friendly view with day and agenda options. Mobile calendar usage is typically higher than desktop because field-based users live in their schedule.

Reporting on calendar data

Reports run on the underlying Event object plus any Object-Based Calendar source. Common reports include Meeting Volume by Rep, Activity by Account, and Calendar Density (events per week per user). The reports sit on standard report types or custom report types built per Object-Based Calendar.

Common pitfalls

Three patterns recur. Users with disabled EAC sync show empty calendars in Salesforce because all their meetings live in Outlook. Object-Based Calendars built on the wrong date field display the wrong records. And calendar over-share (every team member sees every other team member) creates noise that obscures the user's own schedule.

§ 03

How to configure the Calendar for users

The Calendar comes pre-built; the configuration work is in Object-Based Calendars, sharing, and external sync. Get those right and the Calendar becomes operational.

  1. Confirm Event object access

    Users need read/write access to Event to see and create entries. Permission set or profile grants the access.

  2. Add the Calendar component to relevant pages

    App Builder, drop the Calendar component on Lightning Home pages or app launcher tabs where users need quick access.

  3. Build Object-Based Calendars

    From the Calendar UI, create new Object-Based Calendars from objects with date fields. Pick the right date field; the wrong field shows records on the wrong day.

  4. Configure Einstein Activity Capture

    For Outlook/Google sync, enable EAC and assign the permission. Users who do not enable sync see only Salesforce-created Events.

  5. Document sharing conventions

    Decide whether teams share calendars routinely or per request. Over-sharing creates noise; under-sharing leaves coordination friction.

Gotchas
  • Users with EAC disabled see empty Salesforce calendars even when their actual meetings live in Outlook. Confirm sync is enabled for all relevant users.
  • Object-Based Calendars built on the wrong date field show records on the wrong day. Pick the field deliberately.
  • Over-shared calendars become unreadable. Limit sharing to genuine coordination needs.
  • Mobile and desktop calendar behaviour can differ slightly. Test on both surfaces before relying on Calendar workflows.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Calendar.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Discussion

Loading…

Loading discussion…