The pattern: audit in sandbox first, make changes one at a time, communicate to users, monitor for downstream complaints. Activity Settings is low-traffic but the settings cascade across every user's daily workflow.
- Open Activity Settings in sandbox first
Setup, Activity Settings. Document the current state of every toggle. Sandbox first is critical because some changes (Shared Activities) are effectively one-way.
- Walk each setting against current business needs
Shared Activities, reminder defaults, Email-to-Salesforce, Activity Timeline grouping. For each, ask: does this match what reps actually do today?
- Flag toggles that need stakeholder input
Shared Activities (RevOps), reminder defaults (Sales Ops), Email-to-Salesforce vs Activity Capture (depends on org's email integration strategy). These deserve a conversation before changing.
- Make changes one at a time
One toggle, validate downstream behavior, then the next. Two simultaneous changes make it hard to attribute new behavior to a specific change.
- Communicate org-wide changes to users
Settings with per-user overrides do not propagate to users who customized previously. Tell the team what changed and what they may want to update in their own settings.
- Push from sandbox to production through the pipeline
Change sets, source-tracked sandboxes, or DevOps Center. Treat Activity Settings changes the same as any other Setup change.
- Schedule the next quarterly audit
Add the audit to your calendar alongside Account Settings. The quarterly cadence catches drift.
Enables multi-Contact relationships on Tasks and Events. Effectively one-way once enabled.
Whether new Tasks and Events get reminders by default and what the default time is.
The legacy BCC-based email logging feature. Mostly superseded by Einstein Activity Capture for orgs that migrated.
Grouping, field display, completed-activity visibility on the right-rail Activity Timeline component.
Which settings users can override personally and which are locked to the org-wide default.
- Shared Activities is effectively one-way. Enabling cannot be cleanly reversed because historical activity data structure changes.
- Default reminder behavior affects every new activity. Turning reminders on by default for a team that creates dozens of tasks per day produces overwhelming reminder windows.
- Email-to-Salesforce and Einstein Activity Capture serve overlapping needs. Running both creates duplicate activity records; pick one path per email integration.
- Per-user overrides shadow org-wide changes. Users who customized previously keep their customization; admins expecting org-wide propagation are surprised.
- Activity Timeline changes do not apply retroactively to existing customizations on the record page. Some changes require the user to refresh or the admin to re-publish the Lightning page.