Calendar Settings
Calendar Settings is the Salesforce Setup page that controls how user calendars, shared calendars, and public calendars behave across the org: default event reminders, whether events show participant lists by default, the calendar sharing model (private, public read-only, public read/write), enabling Salesforce-side public calendars (Resource Calendars, Public Calendars), and the integration with Lightning Sync or Einstein Activity Capture for external calendar sync.
Definition
Calendar Settings is the Salesforce Setup page that controls how user calendars, shared calendars, and public calendars behave across the org: default event reminders, whether events show participant lists by default, the calendar sharing model (private, public read-only, public read/write), enabling Salesforce-side public calendars (Resource Calendars, Public Calendars), and the integration with Lightning Sync or Einstein Activity Capture for external calendar sync.
Calendar Settings is one of the lower-traffic Setup pages and holds defaults that shape the daily calendar experience for every user. Most settings are reasonable out of the box and rarely need adjustment; the ones that matter are sharing model (public-by-default vs private-by-default affects how reps see colleagues' meetings) and external calendar sync configuration (Lightning Sync, EAC, or third-party). The page deserves a quarterly review alongside Activity Settings and Account Settings to catch drift between platform defaults and team workflow.
Why Calendar Settings is the boring page that quietly shapes daily rep experience
Where Calendar Settings lives and what it covers
Setup, Calendar Settings (or Setup, Activity Settings, Calendar Section depending on edition). The settings cluster into four groups: per-user calendar defaults (reminders, view options, default event duration), sharing model (whether other users can view a rep's calendar by default), public and resource calendars (org-wide calendars users can subscribe to), and external sync (the relationship to Outlook or Google Calendar through Lightning Sync or Einstein Activity Capture).
Calendar sharing model and the visibility default
The default calendar sharing setting (under Sharing Settings, not strictly Calendar Settings but interacting with it) determines whether other users can see a rep's events by default. Private means events are visible only to the owner and people the event is shared with. Public read-only means everyone can see all events. Public read/write means everyone can edit. Most B2B sales orgs run Private or Public read-only; B2C call centers sometimes run Public read/write for shared coverage. The choice shapes the meeting-coordination experience significantly; switching mid-deployment is friction-heavy because reps have already configured their personal calendars to the existing default.
Public Calendars and Resource Calendars
Public Calendars are org-wide calendars users can subscribe to view events: a Marketing Events calendar, a Company Holidays calendar, a Training Schedule calendar. Resource Calendars are Public Calendars associated with shared resources (conference rooms, equipment) where users book the resource by creating an event on the calendar. Both are configured in Setup, Public Calendars and Resources. The feature is largely superseded by Outlook or Google's room booking in most orgs, but persists for orgs that run pure-Salesforce scheduling or for resources that need to appear inside Salesforce specifically.
Default event behavior
Calendar Settings includes per-user default behavior: default event duration (60 minutes is the Salesforce default), default reminder time (15 minutes before is common), whether reminders are on by default. These are org-wide defaults; individual users can override their own preferences. Most teams leave the defaults; the overrides come from individual rep preference. The exception: changing the default event duration to 30 minutes for a team that runs 30-minute meeting culture cuts a click out of every event create.
External calendar sync: Lightning Sync vs Einstein Activity Capture
Lightning Sync (the older feature, deprecated in 2024) syncs events between Outlook or Google and Salesforce. Einstein Activity Capture (EAC, the modern replacement) does the same plus syncs emails, applies AI activity attribution, and feeds Activity data into Einstein for Sales features. Most orgs are on EAC in 2026; Lightning Sync deployments are migrating. Calendar Settings does not directly configure either sync; the sync configuration lives in its own Setup area. Calendar Settings interacts with sync through the default sharing model (synced events inherit the org's default visibility unless the user overrides).
Permissions, per-user overrides, and the change-communication need
Most Calendar Settings have per-user overrides through user preferences. The org-wide default applies to users who have not customized; users who have customized keep their customization across org-wide changes. This matters for change management: an admin who changes the org-wide default expecting all users to see the change finds that long-tenured users keep their existing behavior because they had customized previously. Communicate org-wide calendar changes explicitly to users so they know to revisit their personal settings.
Audit cadence and what to watch for
Quarterly review of Calendar Settings alongside Activity Settings and Account Settings. Specifically: confirm sharing model matches current org practice, confirm default event duration matches the team's actual meeting culture, confirm Public and Resource Calendars are still in use (retiring unused ones reduces clutter), confirm external sync configuration matches the chosen path (EAC for most orgs in 2026). The audit takes 15 minutes and catches drift before it becomes a meeting-coordination complaint.
How to audit and tune Calendar Settings
The pattern: audit in sandbox, change one thing at a time, communicate to users, monitor for adoption. Calendar Settings is low-impact compared to Account Settings but still affects daily rep experience; a 5-minute change can confuse the team for a week if not communicated.
- Open Calendar Settings in sandbox first
Setup, Calendar Settings. Document current state of every toggle and default. Sandbox first lets you test the user experience before changing production.
- Review each setting against current team practice
Sharing model, default event duration, default reminders, Public and Resource Calendars, external sync configuration. Ask whether each matches what the team does today.
- Verify external sync path is on the current product (EAC)
Lightning Sync is deprecated; most orgs should be on Einstein Activity Capture. Confirm the active sync product and migrate if still on Lightning Sync.
- Make changes one at a time
Sharing model change is the highest-impact; treat it as a separate change-control event. Other changes can batch but communicate explicitly.
- Communicate org-wide changes to users
Per-user overrides shadow org-wide changes. Users who customized previously keep their settings; communicate so they know to revisit.
- Retire unused Public and Resource Calendars
Calendars that were created years ago and no one uses add clutter. The Public Calendars list is the audit surface; deactivate what is unused.
- Schedule the next quarterly audit
Add the audit alongside Account Settings and Activity Settings reviews. Quarterly cadence catches drift.
Private, Public read-only, or Public read/write. The highest-impact Calendar Settings choice.
60 minutes default; can be changed to match team meeting culture.
15 minutes before by default; can be adjusted org-wide.
Org-wide calendars users subscribe to. Retire unused ones.
Lightning Sync (deprecated) or Einstein Activity Capture. Most orgs on EAC in 2026.
- Changing the default sharing model mid-deployment confuses reps who have already configured personal calendars to the existing default. Treat as a major change with explicit communication.
- Per-user overrides shadow org-wide changes. Users who customized previously keep their settings; the change does not propagate automatically.
- Lightning Sync is deprecated. Orgs still on it should plan migration to Einstein Activity Capture before forced migration.
- Public and Resource Calendars created years ago often persist long after they stopped being used. Retire unused ones in the quarterly audit.
- Default event duration changes apply only to newly created events. Existing events keep their durations; the change is a workflow tuning, not a data migration.
Trust & references
Cross-checked against the following references.
- Calendar Settings referenceSalesforce
- Activities overviewSalesforce
Straight from the source - Salesforce's reference material on Calendar Settings.
- Calendar SettingsSalesforce Help
- Public Calendars and ResourcesSalesforce Help
- Einstein Activity CaptureSalesforce Help
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.
Test your knowledge
Q1. Why is understanding Calendar Settings important for Salesforce admins?
Q2. What is the primary benefit of Calendar Settings for Salesforce administrators?
Q3. In which area of Salesforce would you typically find Calendar Settings?
Discussion
Loading discussion…