This is a basic overview that explains why some records do not appear as expected in an Activity report, even when users have record access. For example, activity records older than a certain period (the archival period) no longer appear in the report, but they can still be seen on the record page.
Note: Activities captured with Einstein Activity Capture are not visible in core reporting. To view those activities, review the Activities dashboard in CRM Analytics.
This article explains why an Activity report in Salesforce can return unexpected results for some users. The causes include role hierarchy, archiving rules, and filter settings. Review each of the following areas to identify the cause.
Users at any role level can view, edit, and report on all data that is owned by or shared with users below them in their role hierarchy, unless your org's sharing model for an object specifies otherwise.
If an activity's owner does not have an assigned role, the activity does not appear in reports.
To help Salesforce run as efficiently as possible, the following activities are archived and made unavailable in reports, list views, and search:
You can view archived activities on record pages or extract them through the API. To keep activities available longer, increase the Archive Days setting for your organization. See Additional Resources.
Make sure that you use the proper filters and check whether the Contact is private. For example, use "All Activities" instead of "My Activities". If the Contact is private, the related activities show up only for the Contact Owner.
An Activity report can show activities related to an account or contact that was created by a user who is not the owner of that account or contact. When a task is created, the WhatId field (related to records such as Account or Opportunity) or the WhoId field (related to records such as Contact or Lead) is automatically populated. As long as the user has access to the related record, they can view the activities, regardless of whether they own the account or contact.
For example, suppose the Truck account belongs to Jack, and Josh creates a task related to that account. The WhatId field is populated with the ID of the Truck account. When you run an "Accounts with Activities" report, the task that Josh created appears because it is linked to the account.
000386026

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.