Northern Trail Outfitters has the Case Object set to private. The support manager raised a concern the reps have a boarder view of data than expected…

A dynamic dashboard can be configured to (1) run as the logged-in user or (2) let the viewer pick any permitted running user.

If “Let authorized users choose whom they view the dashboard as” is enabled and an admin-level user is selectable, support reps can run the dashboard as that user and therefore see every Case, bypassing the private organization-wide default. This mis-configuration is the most common reason users unexpectedly gain broader data visibility on dashboards.

A. Dashboard Filters – Filters narrow or rearrange the data returned; they never override the underlying row-level security of the running user.

B. Dashboard Subscriptions – Only schedule delivery of an existing dashboard image; they do not change what the dashboard can display.

D. Public Dashboards – Merely place the dashboard in a publicly shared folder; data still respects the running user’s security model.

1. Salesforce Help, “Set Up Dynamic Dashboards” → section “Let authorized users choose whom they view the dashboard as”, Winter ’24 doc ID 000335401.

2. Salesforce Sharing and Visibility Design Guide, “12.2 Dashboard Running User”, pp. 60-61, Winter ’24 (https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/sharingarchitecture.pdf).

3. Salesforce Help, “Control Who Sees What in Dashboards”, paragraph “Running User Determines Data Visibility”, Winter ’24.