Question

Difficulty: MediumDashboard Running User and Visibility Settings

An administrator configures a dashboard to run as a dynamic dashboard so that users see data tailored to their individual record access. A sales user opens the dynamic dashboard and clicks on a chart component to drill down into the underlying source report. How does Salesforce determine what data the user sees on the source report?

  1. The source report displays data strictly according to the logged-in user's own object permissions, role hierarchy, and sharing settings.Answer
  2. B
    The source report automatically inherits the temporary elevated permissions of the dashboard running user, revealing all records shown on the dashboard component.
  3. C
    The source report prompts the user to request permission from the dashboard creator before displaying underlying records.
  4. D
    The source report displays masked data fields for any record the logged-in user cannot access under Organization-Wide Defaults.

Answer

The source report displays data strictly according to the logged-in user's own object permissions, role hierarchy, and sharing settings.
In Salesforce, source reports always execute under the logged-in user's security context. Even if a dynamic dashboard component displays aggregated metrics tailored to the viewer, opening the source report evaluates the logged-in user's object permissions, Organization-Wide Defaults (OWD), role hierarchy, and sharing rules.

Step-by-Step Solution

1
Analyze how dynamic dashboards calculate component metrics.
Dynamic dashboards execute component queries based on the viewing user's security settings.
This allows personalized metrics to display without creating separate dashboards for every user.
2
Evaluate user navigation from dashboard components to source reports.
When a user clicks a component to open the source report, Salesforce opens standard report execution.
Reports always run under the logged-in user's security profile and sharing model.
3
Determine the data visible in the opened report.
The user only sees records they are explicitly allowed to view via OWD, role hierarchy, sharing rules, or manual sharing.
Security settings are strictly enforced at the report level independently of the dashboard context.

Key Concept

Dashboard Running User and Report Security Enforcement
Rate this question