Soru

Zorluk: OrtaDashboard Running User and Visibility Settings

Beacon Logistics Corp enforces an Organization-Wide Default (OWD) sharing setting of Private for the Opportunity object. A Salesforce administrator builds a company-wide executive dashboard and configures the running user as the VP of Sales, who has access to all corporate records. A regional sales representative who owns and has access to only 10 regional opportunities opens the shared dashboard and views a component showing 150 total opportunities nationwide.

What occurs when the regional sales representative clicks this dashboard component to drill down into the underlying source report?

  1. The source report opens and displays only the 10 opportunities that the regional sales representative has permission to access.Cevap
  2. B
    The source report opens and displays all 150 opportunities because it inherits the elevated security access of the dashboard's running user.
  3. C
    An error message is displayed indicating insufficient privileges because the report running user does not match the dashboard running user.
  4. D
    The source report opens, but all record names and monetary amounts are automatically masked with asterisks.

Cevap

The source report opens and displays only the 10 opportunities that the regional sales representative has permission to access.
In Salesforce, while a dashboard component displays data based on the running user specified in the dashboard settings (in this case, the VP of Sales), clicking the component to view the underlying source report forces the report to execute under the security context of the logged-in user. Because the Organization-Wide Default for Opportunities is set to Private and the sales representative only has access to 10 records, the source report will strictly display those 10 records.

Adım Adım Çözüm

1
Analyze the dashboard security context
The dashboard component runs under the VP of Sales' security context (static running user), rendering aggregate metrics for 150 opportunities.
Dashboard components display data according to the permissions of the configured running user.
2
Analyze the source report security context upon drill-down
When navigating to the source report, Salesforce switches to the logged-in user's security context.
Reports always run using the logged-in user's Organization-Wide Defaults, role hierarchy, and explicit sharing rules.
3
Determine final record visibility in the report
The sales representative sees only their 10 accessible opportunities.
Because OWD is Private and the rep only has access to 10 records, the report filters out all remaining unshared records.

Anahtar Kavram

Static Dashboard Running User vs. Source Report Execution Context
Bu soruyu puanla