Examkin

Question

Difficulty: HardDashboard Running User and Visibility Settings

An administrator at Helios Logistics configures a sales performance dashboard stored in a public folder shared with all Regional Sales Managers. To provide managers with a broad overview of company-wide sales trends, the dashboard running user is explicitly set to a static user—the VP of Sales—who holds 'View All Data' administrative permissions. A Regional Sales Manager views the dashboard and clicks on a chart component showing total closed-won opportunities to examine specific deal details. When the underlying source report opens, the manager notices that far fewer records are listed in the report than were summarized in the dashboard chart component. What explains this discrepancy in record visibility between the dashboard component and the source report?

  1. The dashboard component displays aggregated metrics based on the security access of the VP of Sales, whereas the source report evaluates data using the logged-in manager's security access.Answer
  2. B
    Configuring a static running user automatically converts the source report into a dynamic report that restricts rows based on folder permissions.
  3. C
    Viewing a dashboard component grants temporary 'View All' object permissions to the logged-in user, which expire when navigating to the source report.
  4. D
    The source report filter logic automatically overrides the dashboard running user setting to enforce field-level security rules across all summarized fields.

Answer

The dashboard component displays aggregated metrics based on the security access of the VP of Sales, whereas the source report evaluates data using the logged-in manager's security access.
When a dashboard is configured with a static running user (such as the VP of Sales), all users who have folder access to view the dashboard will see component data evaluated using that static running user's security rights. However, when drilling down into the source report behind any component, Salesforce executes the report using the logged-in user's security settings. Because the Regional Sales Manager has restricted record-level sharing compared to the VP of Sales, fewer records are accessible and displayed in the source report.

Step-by-Step Solution

1
Analyze the dashboard running user configuration.
The dashboard is set to run as a static user (VP of Sales) who has 'View All Data' access.
Dashboard components calculate and display metric summaries using the permissions of the specified running user.
2
Analyze source report execution behavior upon drill-down.
When a user clicks a dashboard component, Salesforce launches the source report under the logged-in user's individual security context.
Reports always enforce the viewing user's Organization-Wide Defaults, role hierarchy placement, and active sharing rules.
3
Compare the metric totals between the two views.
The manager sees all company records in the dashboard component via the VP's access, but only sees their own shared records in the source report.
This behavioral difference is by design in Salesforce security architecture for static running user dashboards.

Key Concept

Dashboard Running User vs. Source Report Execution Security
Rate this question

Topics

Dashboard Running User and Visibility Settings

More questions from this topic