Study guide
8.1 Activities, Tasks, Events, Calendar, and Email Productivity
Salesforce Admin Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Platform Administrator Orientation and Official Source Control
1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow
2 Chapter 2: Configuration, Setup, User Management, and Org Controls
2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab
3 Chapter 3: Security, Access, Identity, and Sharing Model
3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab
4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling
4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab
5 Chapter 5: Sales, Marketing, Service, and Support Applications
5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab
6 Chapter 6: Data and Analytics Management
6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab
7 Chapter 7: Automation, Flow, Approval, and Operational Processes
7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab
8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange
8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab
9 Chapter 9: Agentforce for Platform Administrators
9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab
10 Chapter 10: Integrated Salesforce Admin Scenario Labs
10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy
11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy
11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review
8.1 Activities, Tasks, Events, Calendar, and Email Productivity
Key Takeaways Explain This Topic AI
Tasks and events are activity records, but they answer different operational questions: what must be done and what was scheduled.
Activity visibility depends on object relationships, ownership, sharing, calendar access, and enhanced email settings, not only on page layout placement.
Email productivity features help adoption only when the admin defines logging expectations, template governance, deliverability controls, and support ownership.
Admins should troubleshoot activities by checking permissions, related records, user settings, automation, and whether the issue is UI, sync, or data visibility.
Last updated: May 2026
Activities as operational evidence
Activities are where many users feel Salesforce either helps them or slows them down. Tasks represent work to complete, such as calling a prospect, sending a renewal quote, or following up after a case escalation. Events represent scheduled time, such as a discovery meeting, implementation review, onsite visit, or internal account planning session. Together they create an activity history that managers, sales teams, service teams, and support leaders use to understand whether important work is moving.
The admin's job is to make this history useful without overloading users. A page layout with every activity related list visible does not guarantee adoption. Users need the right quick actions, compact layouts, activity timeline fields, default values, reminders, and list views. Managers need consistent definitions for open tasks, overdue tasks, completed activities, meeting count, and next step quality. Support teams need to know where to look when a user says a meeting disappeared or an email did not log.
Productivity need Primary feature Admin consideration
Track follow-up work Tasks Due date, priority, status, owner, reminders, queues, and automation impact.
Track scheduled meetings Events and calendars Attendee behavior, related records, sharing, and calendar visibility.
Review past interactions Activity Timeline Related record links, completed activities, filters, and page placement.
Send repeatable messages Email templates and quick text where available Folder access, merge fields, branding, approval, and maintenance ownership.
Log customer emails Enhanced Email, email integration, or manual logging Data storage, privacy expectations, user training, and troubleshooting path.
Coordinate team availability Calendars and public calendars Sharing model, resource calendars, and delegated administration.
Setup navigation depends on the exact feature. Activity settings are typically reviewed from Setup > Activity Settings . Task and event fields are managed from Object Manager > Task and Object Manager > Event . Email deliverability is checked from Setup > Deliverability . Organization-wide email addresses, email templates, and Lightning email settings have their own setup areas. The exam-level skill is not memorizing every click. It is knowing which family of settings controls the outcome.
Activities are also data. They can be imported, reported on, archived, deleted, and affected by automation. If leadership asks why account teams are not logging meetings, the admin should inspect whether users have an easy action on Account, Contact, Lead, Opportunity, and Case pages. If users complain that they cannot edit completed tasks, check object permissions, record ownership, sharing, page layout fields, validation rules, and record-triggered automation before assuming the activity timeline is broken.
Email and calendar support workflow
Email productivity is a governance topic, not just a convenience feature. Salesforce can support email templates, logged emails, email-to-record relationships, organization-wide sender addresses, quick text, and integrations with external email and calendar systems. The admin must decide which messages should be standardized, who can edit shared templates, whether emails should be logged automatically or manually, and how sensitive email content is handled. A regulated support process may require different controls than a sales development process.
A practical admin workflow for an email productivity rollout:
Identify the user groups, objects, and customer communication types in scope.
Confirm whether users need to send from Salesforce, log from an inbox, use templates, or synchronize calendar events.
Review email deliverability, org-wide email addresses, compliance settings, and authentication requirements with the technical owner.
Configure templates, quick actions, page layouts, and Lightning record pages so users can work from the record they already use.
Test as users with different profiles, permission sets, record access, and email addresses.
Create a support checklist for missing emails, failed sends, duplicated logs, and sync conflicts.
Monitor adoption with reports on activities, template use where available, and overdue follow-up work.
Calendar and email integrations create scenario traps because users experience them as one workflow even when several systems are involved. A meeting may exist in an external calendar but not in Salesforce. An email may have been sent from an inbox but never related to the opportunity. A logged email may be visible to one user and hidden from another because the related record is private or the email record is associated differently than expected. The admin should separate user interface behavior, sync behavior, and record visibility.
Ownership matters. A task owned by a user appears in that user's work queue, but it may be related to an account, opportunity, contact, lead, or case that has its own sharing rules. Events can have invitees and related records, but a user's ability to see the context still depends on access. Public calendars and resource calendars can help teams coordinate, but they should be maintained deliberately. Stale calendars reduce trust quickly.
For hands-on practice, create a Trailhead Playground account, contact, opportunity, and case. Add tasks with different owners, due dates, priorities, and statuses. Add events related to different records. Send or log sample emails if your playground supports the feature. Then build reports for open tasks by owner, overdue follow-up by account segment, and completed activities this month. The learning goal is to connect Setup choices to user adoption and reporting quality.
Study trap: do not assume an email or event problem is solved by giving broader object access. Start with the feature setting, user permission, related record, ownership, sync path, and expected behavior. Broad permissions may hide the symptom while creating a security problem.