Calendar
A Calendar in Salesforce is the scheduling surface in Lightning Experience that shows your Event records, plus any object calendars built from other records that carry a date field, in day, week, and month views.
Definition
A Calendar in Salesforce is the scheduling surface in Lightning Experience that shows your Event records, plus any object calendars built from other records that carry a date field, in day, week, and month views. It lives as the Calendar tab and as a Calendar component you can drop onto a Lightning page. You always see your own events, and you can layer on calendars that other people share with you or that an admin builds from object data.
The Calendar matters because schedule information is scattered across the org. Meetings sit in Event records, opportunity close dates sit on Opportunity, and field bookings sit on Service Appointment. The Calendar pulls those into one timeline through object calendars and external sync, so a rep does not have to check five places to see what is happening this week.
How the Salesforce Calendar is put together
Your personal calendar and the Event object
The base layer of the Calendar is your own set of Event records. An Event is a standard Salesforce activity with a Subject, Start and End date or time, an All-Day Event flag, Location, and a Reminder. It can be related to a record through the Name field (a contact or lead) and the Related To field (an account, opportunity, case, or custom object). When you create an event from the Calendar, Salesforce drops it on the timeline and also lists it on the related record's activity timeline, so the meeting shows up wherever you look for it. You can create an event by clicking the New Event button or by clicking directly on a time slot, which prefills the start and end times for you. Events you do not own can still appear if their owner shares a calendar with you. The personal calendar is per user, so two reps looking at the same Calendar tab see different events. Everything else, shared calendars and object calendars, layers on top of this personal base.
Object calendars from any date field
An object calendar turns records from a standard or custom object into calendar entries, using a date or date/time field to place them. A common build shows Opportunities by Close Date, Service Appointments by Scheduled Start, or a custom object's due date. You pick a start date field and, if the object has one, an end date field, then choose the field whose value labels each entry. You can also point the calendar at an existing list view so it only shows the records that view returns. Object calendars are personal to the user who creates them, and each user can create up to 10. A few limits are worth knowing. The calendar displays a capped number of items per view (Salesforce documents a 150-record limit), so a busy object can hide records past the cap. External objects and encrypted field values are not supported as the source. Records still obey your sharing and field-level security, so an object calendar never exposes data a user could not already see on the record itself.
Sharing your calendar with coworkers
You can give specific people access to your personal calendar so they see your events alongside their own. Sharing is done from the calendar's own sharing settings, and you grant a Calendar Access level to a user, a role, or a public group. The levels run from Hide Details (the viewer sees only that you are busy) up through Show Details, Show Details and Add Events, and finally full access where the viewer can add and edit events. Which options appear depends on the Calendar object's organization-wide default. If the org-wide default is set to Hide and Add Events, the broader sharing choices may be missing until an admin loosens the Default Internal Access for the Calendar object in Sharing Settings. This is the usual reason a user complains that the sharing dropdown is short. Sharing one user's calendar is different from a public calendar, which an admin creates for a team or a resource like a conference room. Both end up as extra calendars a user can switch on, but they are configured in different places.
Syncing Outlook and Google with Einstein Activity Capture
Many people run their real schedule in Outlook or Google, not in Salesforce. Einstein Activity Capture connects those external calendars so the meetings appear inside the Salesforce Calendar without manual re-entry. Once a user connects an account, their external events flow in and, depending on configuration, changes can flow back out. Without this sync, the Salesforce Calendar shows only events that were created in Salesforce, which is why a freshly onboarded rep often sees an empty week even though their Outlook is full. Activity Capture handles the calendar sync and also captures emails against related records, so it does more than the Calendar alone. There are nuances about which direction edits travel and what data is stored, and those live in the Activity Capture documentation rather than the Calendar docs. The practical takeaway for admins is simple. If a user's meetings live outside Salesforce, turn on the sync, or the Calendar will look broken to that user even though it is working as designed.
Where the Calendar plugs into other products
The Calendar is not just a personal planner. It is the display surface for several scheduling products. Salesforce Scheduler writes its Service Appointment bookings to the Calendar through event management, so a banker or advisor sees their booked slots in the same view as their other events, and changes to an appointment update the calendar entry. Field Service uses Service Appointment records too, and a dispatcher or technician can surface those through an object calendar to see the day's jobs. Because all of these sit on standard activity and appointment objects, the Calendar treats them like any other entry, which keeps the experience consistent for the user. You can also embed the Calendar component on a home page or an app page so a team lands on their schedule when they log in. For a developer, the lightning__CalendarService and related Lightning APIs let custom components read and create calendar events on supported clients, which is how mobile and custom apps interact with the same data.
Mobile, views, and reporting
The Salesforce mobile app renders the Calendar in a touch-friendly layout with day and agenda options, which suits field-based users who live in their schedule away from a desk. On desktop, the Calendar offers day, week, and month views, and you can drag an event to a new slot or resize it to change its duration. Reporting on calendar activity does not run against the Calendar itself but against the underlying objects. You report on the Event object for meeting volume, and on whatever object backs an object calendar (Opportunity, Service Appointment, or a custom object) for the records shown there. Useful reports include meetings per rep per week, activities logged against top accounts, and appointment counts by service territory. Because object calendars can be built on a list view, admins sometimes pair a sharp list view with a calendar so a team sees exactly the records that matter, such as appointments for one territory or opportunities closing this quarter, without the noise of everything else.
Common pitfalls and how to avoid them
A handful of issues come up again and again. The first is the empty calendar, almost always caused by missing Einstein Activity Capture sync, so the user's Outlook or Google meetings never reach Salesforce. The fix is to connect the account. The second is an object calendar built on the wrong date field, which scatters records onto the wrong days. Check that the start date field you chose is the one users think of as the event date, and that any end date field comes after the start, or the record will not render. The third is the record cap. A high-volume object can push records past the per-view display limit, so a calendar can look incomplete. Narrow it with a tight list view so the records you care about stay under the cap. The fourth is over-sharing. If everyone shares full calendars with everyone, each user's view fills with other people's events and the signal drowns. Share only where coordination genuinely needs it, and prefer a public calendar for shared team resources rather than cross-sharing every individual.
Create an object calendar in Lightning Experience
An object calendar surfaces records from any standard or custom object as calendar entries, using a date field to place them. Here is how a user creates one in Lightning Experience. Each user can create up to 10 of their own.
- Open the Calendar tab
Click the Calendar tab in the app navigation. If it is not visible, an admin may need to add it to the app or enable it for the profile.
- Start a new calendar
Click the gear or settings icon next to My Calendars in the left side panel and choose New Calendar.
- Pick the object
Select the standard or custom object whose records you want to show, for example Opportunity, Service Appointment, or a custom object. External objects are not supported.
- Map the fields
Choose the field that names each entry, the start date or date/time field, and an end date field if the object has one. Optionally apply an existing list view to filter the records.
- Save and toggle it on
Save the calendar. It appears under Other Calendars where you can show or hide it and change its color so its entries are easy to tell apart from your events.
The standard or custom object the calendar draws records from. External objects and some special objects are not eligible.
The record field whose value labels each entry on the calendar, such as Subject or Name.
The date or date/time field that decides where each record lands on the timeline.
A second date field that gives each entry a duration. It must fall after the start, or the record will not display.
An existing list view that filters which records appear, useful for keeping a busy object under the display cap.
- An object calendar shows a capped number of items per view (Salesforce documents 150). Use a narrow list view so important records do not fall past the cap.
- If the end date field is earlier than the start date field, the record silently does not appear on the calendar.
- Object calendars respect record sharing and field-level security, so a user only sees records they could already open. They never widen access.
- Each user creates and owns their own object calendars, up to 10, so there is no single org-wide object calendar to manage centrally.
Prefer this walkthrough as its own page? How to Calendar in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Calendar.
- Calendar Views in Lightning ExperienceSalesforce
- Calendar Sharing in Lightning ExperienceSalesforce
Hands-on resources to go deeper on Calendar.
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 discussion…