Aegis Solar Solutions enforces a Private sharing model for Opportunities. A Salesforce administrator configures an executive sales dashboard to run as a static user, specifically the VP of Sales. When sales representatives view this dashboard and interact with its components, which two statements accurately describe how data visibility and security are applied? (Select 2 options.)
- Dashboard components display summarized metrics reflecting all records accessible to the static running user, regardless of the viewer's individual sharing access.Cevap
- Clicking a dashboard component opens the underlying source report, which displays only the records accessible to the logged-in viewer based on their own record-level security.Cevap
- CDrilling down into the source report temporarily expands the viewer's security access to match the running user's access for all detailed record rows.
- DUsers who lack access to the dashboard folder can still view dashboard components if the static running user has Administrative access to the folder.
- EThe static dashboard automatically converts to a dynamic dashboard when accessed by users who do not hold the View All Data permission.
Cevap
The correct statements are that dashboard components display summarized metrics reflecting all records accessible to the static running user, and clicking a component to open the source report restricts the detailed view to records accessible under the logged-in user's security context.
When a dashboard is set to run as a static user, the component summaries display data based on that running user's permissions, enabling viewers to see aggregated metrics for records beyond their personal sharing access. However, source reports always run under the logged-in user's security context. Therefore, when a user clicks a component to view the source report, Salesforce enforces the viewer's own Organization-Wide Defaults and sharing rules, displaying only the individual records they are authorized to see.
Adım Adım Çözüm
Anahtar Kavram
Static Dashboard Running User vs. Source Report Execution Context