Building a Dynamic Dashboard takes the same time as building any dashboard. The Dynamic part is a single toggle in the properties. The harder work is designing the underlying reports to surface useful data per-viewer.
- Create the underlying reports
Build the source reports first. A Dynamic Dashboard typically uses reports that filter by My records or My team''s records (Owner = $User.Id, Owner = $User.Manager.Id, or via record-level sharing). The reports must respect the viewer''s permissions, so design them to use $User merge fields where appropriate.
- Create the dashboard
From the App Launcher, open Dashboards. Click New Dashboard. Give it a name and pick a folder to save it in.
- Set View dashboard as to Logged-in user
In the dashboard properties (gear icon), set View dashboard as to Logged-in user. This is the key step that makes the dashboard Dynamic. Save.
- Add components
Drag chart and table components onto the dashboard. Each component picks a source report. The Dynamic property carries through; viewers will see only the records each report scope allows them to see.
- Share the dashboard with the right audience
Set folder sharing or dashboard-level sharing to grant access to your viewers. Profiles, public groups, or roles all work.
- Test as different users
Use Login As (or test accounts with different profiles) to confirm each viewer sees the right data. A rep should see only their pipeline; their manager should see all team pipelines; a leader should see the whole region.
Each viewer sees data filtered by their own access. The Dynamic Dashboard setting.
All viewers see data filtered by the named Running User. The default for non-Dynamic dashboards.
Each viewer sees data through the dashboard creator''s lens. Less common; usually a setup mistake.
Controls who can open the dashboard. Distinct from the data-access filter.
- Dynamic Dashboards cannot be emailed or scheduled. If stakeholders need a weekly dashboard digest, you need a standard dashboard or a custom email workflow.
- Each org has a Dynamic Dashboard limit (5 on Enterprise, 10 on Unlimited). Hitting the limit means converting non-essential dashboards back to standard.
- Performance can suffer for individual viewers with complex sharing. A user with access to 200,000 records may experience slow rendering compared with a user with access to 200 records.
- Subscribers and Chatter-feed integrations do not work on Dynamic Dashboards. The dashboard has no fixed Running User, so subscription-based features cannot bind to anyone.