Examkin

Question

Difficulty: MediumDashboard Running User and Visibility Settings

Velox Energy Solutions enforces an Organization-Wide Default (OWD) sharing setting of Private for Opportunities. The executive team wants sales managers to view a high-level summary of total company pipeline on a shared dashboard. However, when a sales manager clicks on a dashboard component to open the underlying source report, they must only see individual opportunity records that they own or share access to. Which dashboard configuration meets these security requirements?

  1. Configure the dashboard with a static running user who has access to all opportunities.Answer
  2. B
    Configure the dashboard as a dynamic dashboard set to run as the logged-in user.
  3. C
    Modify the Opportunity Organization-Wide Default setting from Private to Public Read-Only for all sales managers.
  4. D
    Assign the View All Data administrative permission to all sales managers on their user profile.

Answer

Configure the dashboard with a static running user who has access to all opportunities.
In Salesforce analytics, dashboard components execute under the security context of the configured Running User. Setting a static running user with access to company-wide opportunity data allows dashboard components to display aggregate pipeline summaries to all viewers. However, when users click a component to view the source report, the report runs under the logged-in user's security context, enforcing Organization-Wide Defaults and sharing rules so managers only view individual detail rows they are permitted to see.

Step-by-Step Solution

1
Analyze the requirement for aggregate metrics versus detailed record security.
Dashboard components must display aggregated pipeline totals across the company, but source reports must restrict detailed row data based on user access.
Salesforce dashboard components run under the security context of the dashboard running user, whereas source reports run under the context of the logged-in user.
2
Evaluate static running user configuration.
Setting a static running user with broad access (such as a VP of Sales) ensures dashboard component summaries aggregate all pipeline data for viewers.
Components render data using the static running user's security permissions.
3
Verify source report drill-down security behavior.
When a sales manager clicks into the source report, Salesforce evaluates record sharing using the logged-in user's profile, OWD, and sharing settings, showing only authorized records.
Source reports never execute using the dashboard running user's context; they always enforce the viewing user's permissions.

Key Concept

Dashboard Running User vs. Source Report Execution Context
Estimated Time:1m 30s
Rate this question

Topics

Dashboard Running User and Visibility Settings

More questions from this topic