Apex Financial Solutions utilizes a central pipeline dashboard to display sales performance across global territories. The dashboard is saved in a shared folder accessible to all Sales Managers with 'View' access and is configured to run under a static running user—the Vice President of Global Sales, who possesses full organization-wide visibility across all Account and Opportunity records. The Salesforce administrator is considering switching this dashboard from a static running user to run as a dynamic dashboard ('Run as the logged-in user'). Which two statements accurately describe the data access and operational behavior under these configurations? (Select 2 options)
- When viewing the dashboard under the static running user, Sales Managers see aggregated component data reflecting the Vice President's access level, but clicking through to the underlying report evaluates data visibility using the logged-in user's own permissions.Answer
- Configuring the dashboard to 'Run as the logged-in user' prevents administrators from setting up scheduled email refreshes for dashboard subscribers.Answer
- CViewing a dashboard configured with a static running user permanently grants the viewing user underlying record-level sharing access to all records displayed in the dashboard components.
- DDrilling down into an underlying report from a dynamic dashboard component automatically overrides Organization-Wide Defaults to match the folder manager's administrative privileges.
- EUsers assigned the 'Manage Dashboards' permission can bypass the organization's maximum limit of dynamic dashboards by storing them in their personal dashboard folders.
Answer
The correct options state that dashboard components under a static running user display metrics based on that specified user while underlying report drill-downs enforce logged-in user permissions, and that switching to a dynamic dashboard disables scheduled email refreshes.
Dashboard components running under a static running user display summarized metrics using the specified running user's security rights, but clicking into the underlying report executes the report under the viewing user's own security context. Furthermore, dynamic dashboards ('Run as the logged-in user') dynamically calculate data for each viewer and therefore cannot be scheduled for automated email subscriptions or refreshes.
Step-by-Step Solution
Key Concept
Dashboard Running User Security and Dynamic Dashboard Limitations
Estimated Time:2m 0s