Choose 1 option. Cumulus Pharma uses Agentforce Life Sciences for Customer Engagement to provide Account Summaries. The Agentforce Life Sciences…

The issue stems from how the "Cross-Object Field History Graph" component is configured on the Account Lightning Record Page, not from data access permissions. Lightning page components can have visibility rules that control whether they are displayed based on the viewing user's profile, role, or permissions. In this scenario, the consultant likely configured the component's visibility to display only for the "Key Account Manager" profile, but not for the "field sales rep" profile. Therefore, the reps' summary page does not render this specific component, effectively excluding the visit and inquiry data.

B. The field sales rep has not been added to a Data 360 segment used for summarization.: This is less likely, as Data 360 is a separate product and the issue is described in the context of a specific graph component's configuration.

C. The field sales rep profile does not have View All permissions on these objects.: While this would cause missing data, the user already has "Read" access. The more direct cause for a component's data being entirely excluded for one profile is a component visibility rule.

1. Salesforce Help. "Dynamic Lightning Pages". This document explains how to set component visibility filters on Lightning record pages. It states, "You can make your Lightning record pages more dynamic by configuring component visibility filters...For example, you can create a rule for a component to appear only when a record’s field has a specific value, or when the viewing user is in a specific role or profile." This directly supports the explanation.

2. Salesforce Platform App Builder Certification Guide. Section: "User Interface". This guide covers the configuration of Lightning App Builder, including setting visibility for components based on user attributes like Profile.