Examkin

Question

Difficulty: HardDashboard Running User and Visibility Settings

Zenith Wealth Management enforces a Private Organization-Wide Default (OWD) sharing model for Opportunities. A Salesforce administrator configures an executive performance dashboard stored in a shared folder accessible by all Sales Managers. The dashboard's running user is statically set to the Chief Commercial Officer (CCO). When a Sales Manager views the dashboard component, it displays 25,000,000intotalpipelinevalue.However,whentheSalesManagerclicksthecomponenttoopentheunderlyingsourcereport,thereportdisplaysonly25,000,000 in total pipeline value. However, when the Sales Manager clicks the component to open the underlying source report, the report displays only 4,500,000 in pipeline value. Which statement explains the primary cause of this discrepancy?

  1. The dashboard component calculates results using the record-level security of the static running user, while the source report executes using the security context of the logged-in user.Answer
  2. B
    The underlying source report automatically converts to a dynamic report filter, which removes records outside the Sales Manager's immediate role hierarchy branch.
  3. C
    Opening a static dashboard component temporarily grants View All access to the component summary, but the access revokes as soon as the user navigates away from the dashboard.
  4. D
    The shared folder containing the dashboard grants View access, which overrides the Private Organization-Wide Defaults for dashboard components but not for report folders.

Answer

The dashboard component calculates results using the record-level security of the static running user, while the source report executes using the security context of the logged-in user.
When a dashboard is configured with a static running user, component metrics are calculated using that specified user's security access level (the CCO), allowing viewers to see summarized metrics they might not individually own. However, when a user clicks the component to open the source report, Salesforce runs the report using the logged-in user's security context, restricting record display to only what the user can access under OWD and sharing rules.

Step-by-Step Solution

1
Analyze how static dashboard running user settings affect component data visibility.
When a dashboard is configured with a static running user (such as the CCO), all users with folder view access see summary data aggregated according to the CCO's record access permissions ($25,000,000).
Static running users determine the security context used to calculate component metrics.
2
Analyze how source report execution handles user record permissions upon drill-down.
When clicking a dashboard component to view the source report, Salesforce runs the report under the logged-in user's own security context (Sales Manager).
Source reports always enforce individual record-level access based on OWD, sharing rules, and role hierarchy for the logged-in user ($4,500,000).
3
Identify the cause of the data discrepancy between the dashboard component and the source report.
The discrepancy occurs because the dashboard displays data using the CCO's access while the source report displays data using the logged-in Sales Manager's access.
This is standard platform behavior when using static running users on objects with restricted sharing.

Key Concept

Static dashboard components render data according to the designated running user's security context, whereas underlying source reports always execute based on the logged-in user's security access.
Rate this question

Topics

Dashboard Running User and Visibility Settings

More questions from this topic