Tasks
Tasks is both a Setup area where administrators configure the behavior of task records across the org and the standard Task object itself that captures to-do items, follow-ups, calls, emails, and other activities the team needs to track.
Definition
Tasks is both a Setup area where administrators configure the behavior of task records across the org and the standard Task object itself that captures to-do items, follow-ups, calls, emails, and other activities the team needs to track. The Setup-side configuration controls how tasks behave at the platform level: default notification settings when a task is assigned, what happens when a task is completed, archival rules for old tasks, and the visibility of completed-versus-open tasks across record-detail pages.
The Task object is one of the most heavily used standard objects in Salesforce because it is the canonical place to record any action a user takes related to a Lead, Contact, Account, Opportunity, Case, or any other record. Logged calls become Task records. Sent emails become Task records (alongside their Email Message counterparts). Manually entered to-dos become Task records. The combination of Setup configuration plus Task object behavior shapes how the entire org tracks activity and follow-up, which makes it a foundational element of sales productivity, service responsiveness, and operational analytics.
The Task object and its configuration surface
Standard Task fields and structure
Each Task record carries a Subject (the action description), Due Date, Status (Open, Completed, Deferred), Priority, Type (Call, Email, Meeting, etc.), Owner (the user responsible), and WhoId (Lead or Contact related to the task) plus WhatId (any other related record like Account, Opportunity, Case). The dual related-record fields are a quirk of the Task object: a single task can be tied to one Contact and one Opportunity simultaneously, with the WhoId and WhatId fields serving as the two anchors. Standard fields support most use cases; custom fields are common for adding business-specific tracking (call disposition, outcome notes, related campaign).
Task assignment notifications
When a task is assigned to a user, the platform optionally sends an email notification to the assignee with a link to the task and the related record. The notification behavior is controlled by org-wide settings (a default for whether all task assignments send email) and user-level preferences (each user can override the default for their own assignments). Most enterprises leave the default at "send notification" but allow users to opt out if they prefer to manage tasks through other channels (the Salesforce mobile app, integrated calendar tools, custom workflow). The notification configuration sits under Activity Settings in Setup.
Task completion behavior
When a user marks a task as Completed, the platform updates the Status field and the ActivityDate to the completion date. Configuration controls whether completed tasks remain visible on the related record's activity timeline, whether they are archived to a separate view, and whether any post-completion automation fires (notifications, follow-up task creation, related record updates). Mature sales orgs use the completion event to trigger downstream automation: marking the related Opportunity as having activity in the last 7 days, scoring the Lead for engagement, updating the Account's last touch date. The completion configuration is the glue between task tracking and the broader activity-driven workflow.
Recurring tasks
The standard Task object supports recurring tasks: a task that repeats daily, weekly, monthly, or yearly with a defined end date or until a specific occurrence count. Each recurrence creates a new Task record on its scheduled date. Recurring tasks are useful for routine follow-ups (a quarterly business review reminder for each strategic account, a monthly compliance check for each regulated record). The recurrence configuration is set when creating the task, with the underlying records linked through the RecurrenceActivityId field on the Task object. Recurring tasks have their own quirks around editing (changes can apply to one occurrence or to all future occurrences) that admins should understand.
Activity timeline integration
Tasks appear in the Activity Timeline component on record detail pages alongside Events, Email Messages, Logged Calls, and other activity records. The timeline shows both open tasks (sorted by due date) and completed tasks (sorted by completion date) with filters for activity type, owner, and date range. The timeline is the day-to-day interface most users interact with for task management, and customizing it (sort order, default filters, custom activity types) is a standard part of any Service Console or Sales Console implementation. Lightning App Builder lets admins control which Activity Timeline appears on which page layout.
Reporting on tasks
The standard report types on Task support a wide range of analytics: tasks completed by user this week, tasks overdue per Account, tasks by type and outcome, task volume trends per team. These reports power the productivity dashboards that sales managers and service supervisors rely on for daily and weekly review. Custom report types extend the standard set to include task-related fields from custom objects or to combine tasks with their related Opportunities or Cases. CRM Analytics dashboards push the analytics further with cohort views and time-series patterns. The breadth of task reporting is what makes Tasks a primary source of operational insight in most orgs.
Task data volume and archival
Tasks are a high-volume object. Every call logged, every email sent through Salesforce, and every manually created to-do becomes a Task record. Long-running orgs accumulate millions of Task records, which can affect storage, query performance, and the responsiveness of activity timelines on busy records. Salesforce provides archival options for old tasks: archive after a configurable retention period (typically 365 days), with archived tasks remaining queryable but excluded from default views and timelines. Configuring the archival policy is part of mature task management: balance the storage and performance benefits of archival against the operational need to see historical activity.
Tasks versus Events and the broader Activity model
The Activity model in Salesforce includes both Tasks and Events, which serve overlapping but distinct purposes. Tasks are typically asynchronous (a to-do item, a call to make, an email to send) and have a due date but not a fixed time. Events are time-blocked (a meeting from 2 PM to 3 PM, a scheduled call at a specific time, a conference session) and represent calendar entries that may sync with Outlook or Google Calendar. Both objects appear in the Activity Timeline and both share many design patterns. Choosing between Task and Event is usually a question of whether the activity is anchored to a specific calendar slot (Event) or anchored to a deadline without a specific time (Task). The third related object, Email Message, captures the content of emails sent through Salesforce email tools, with the Task record representing the send action and the Email Message storing the body. Mature orgs use all three together: Tasks for to-dos and outbound activities, Events for scheduled meetings, Email Messages for email body and rendering. The Activity Settings configuration shapes how the three interact and how they appear to users. Beyond the standard three, custom objects sometimes layer on top to track activity types that do not map cleanly to Task or Event semantics. For most organizations, the standard model handles the use cases, but the option to extend exists.
Configure Tasks for the org
Setting up Tasks well involves both the Setup-side configuration and the operational practices that make tasks useful in daily workflow. The workflow below covers the standard sequence for a service-or-sales-focused org rolling out task management.
- Configure default task settings in Activity Settings
From Setup, navigate to Activity Settings. Configure the default behavior for task assignments: whether email notification is sent, whether completed tasks are kept on the timeline, whether the daily task email summary is enabled. Configure the org's recurrence permissions: which users can create recurring tasks. Save the settings and confirm in sandbox that the defaults behave as expected. Adjust user-level preferences for users who need different behavior than the org default.
- Customize the Task object fields and layouts
Open the Task object in Object Manager. Review the standard fields and add custom fields the org needs: outcome dispositions, scripted call notes, related campaign or product, custom subject taxonomy. Configure the page layout to show the right fields for each Task record type (if record types are used). Add custom buttons or quick actions for common task operations (Log Call, Schedule Follow-up, Mark Complete with Outcome). Test the layout with a sample task and confirm the experience is clean.
- Configure Activity Timeline on record pages
For each parent object where tasks appear (Account, Contact, Opportunity, Case, Lead), open the Lightning page in App Builder. Add or configure the Activity Timeline component. Set default filters (show only open tasks, or both open and completed). Configure the sort order. Add quick actions for fast task creation directly from the parent record. Save the page and assign it to the relevant app and profile. Test from a sample parent record to confirm the timeline behaves as expected.
- Build reports and dashboards on tasks
Create the standard task reports the operations team will use: completed tasks this week per rep, open tasks by due date, overdue tasks per Account, task volume trends. Build dashboards that combine these reports for sales managers and service supervisors. Schedule the dashboards to be reviewed in the team's weekly cadence. Without active reporting, task data accumulates but does not drive operational behavior; the reports are what make the configuration valuable.
- Task is a special object with limits and behaviors different from standard custom objects. Bulk operations and Apex against Task have their own performance characteristics.
- WhoId and WhatId are dual relationship fields. Custom code needs to handle both correctly; many bugs trace back to assuming only one is populated.
- Recurring tasks create one record per occurrence. High-frequency recurrence on many parent records can rapidly grow the Task table.
- Activity Timeline performance degrades on records with thousands of related tasks. Archive old tasks or filter the timeline to recent activity for these records.
- Email notifications on task assignment add to the org's daily email allocation. High-volume assignment workflows can hit limits.
Trust & references
Straight from the source - Salesforce's reference material on Tasks.
- TasksSalesforce Help
- Activity SettingsSalesforce 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 Tasks important for Salesforce admins?
Q2. In which area of Salesforce would you typically find Tasks?
Q3. What is the primary benefit of Tasks for Salesforce administrators?
Discussion
Loading discussion…