Apex Pinnacle Logistics maintains a Private sharing model for Accounts and Opportunities. A Salesforce administrator configures a company-wide sales dashboard and specifies the VP of Sales as the static running user. A regional sales representative opens the dashboard and views metric components showing total national sales totals. However, when the representative clicks a dashboard component to drill down into the underlying source report, the report displays only the opportunities owned by their regional team. What explains this difference in record visibility between the dashboard component and the source report?
- The dashboard components render using the static running user's security access, whereas the underlying source report executes using the viewing user's individual sharing permissions.Answer
- BSetting a static running user temporarily elevates the viewing user's profile permissions to match the running user across both dashboard components and source reports.
- CThe source report automatically inherits access rights from the running user only if the dashboard is configured as a dynamic dashboard.
- DThe viewing user lacks 'Run Reports' permission, which prevents source reports from rendering data beyond their explicit role hierarchy level.
Answer
The dashboard components render using the static running user's security access, whereas the underlying source report executes using the viewing user's individual sharing permissions.
In Salesforce analytics, static running users dictate the security access used to calculate and display dashboard components. When users view the dashboard, component totals reflect what the static running user (VP of Sales) can see. When drilling down into the underlying source report, Salesforce runs the report using the viewing user's own security rights, causing records restricted by sharing settings to be hidden.
Step-by-Step Solution
Key Concept
Dashboard Running User vs. Source Report Security Context
Estimated Time:1m 15s