Dashboard Widget
A Dashboard Widget in Salesforce, also called a Dashboard Component, is one of the individual visual tiles inside a Lightning Experience or Classic dashboard that renders data from a single source report.
Definition
A Dashboard Widget in Salesforce, also called a Dashboard Component, is one of the individual visual tiles inside a Lightning Experience or Classic dashboard that renders data from a single source report. Each widget pulls rows from its report and displays them as a chart, gauge, metric, or table. A dashboard is a layout of multiple widgets; widgets share filters and refresh together but are configured independently.
Dashboards exist to surface report data in a way that is faster to scan than the underlying tabular report. A Dashboard Widget condenses a report into one bar chart, donut, metric tile, or summary table that a leader can read at a glance. Salesforce ships a fixed set of widget types (line, bar, donut, pie, funnel, scatter, gauge, metric, table, Lightning Component); each maps to a different visual pattern. The dashboard editor is drag-and-drop; building a widget requires picking a source report, choosing a widget type, and configuring axis or sort settings.
How Dashboard Widgets work in Salesforce
Source report and the widget layer
Every widget points at exactly one source report. The widget rendering layer reads the report rows, applies the widget configuration (chart type, axis, sort, top N), and draws the chart. Changes to the source report (filters, columns, grouping) propagate to the widget on next refresh. Widgets cannot pull data from outside a report; this is sometimes a limitation when a complex dashboard wants computed cross-report values.
Widget types and when to use each
Charts (bar, line, donut, pie, funnel, scatter) visualize comparisons and trends. Gauges and metrics surface single KPIs. Tables show raw rows when the data does not summarize well. Lightning Component widgets (custom LWC or AppBuilder components) extend the standard set for use cases that need interactive visuals or external data. Pick by what question the leader is trying to answer: comparison, trend, threshold, or specific values.
Filters and dashboard-level controls
Dashboards support up to three dashboard-level filters that propagate to every widget. The filter is a per-dashboard customization that overrides the source report filter. This enables one dashboard to show pipeline by region, by stage, by quarter without rebuilding the underlying reports.
Dynamic vs static dashboards
A standard dashboard shows the same data for every user. A Dynamic Dashboard runs as the viewing user, so the data scopes to what that user can see. Dynamic dashboards are useful for sales-leader dashboards where each leader sees their team. They are licensed per dashboard (each org has a cap on dynamic dashboards).
Refresh frequency and the data lag
Dashboard widgets do not refresh in real time. They refresh on a schedule (default daily, configurable per user up to subscriptions) or on manual click. The data displayed is from the last refresh. This is fine for executive dashboards but surprises users who expect real-time data. Plan around it.
Lightning Dashboards vs Classic Dashboards
Lightning Experience introduced a redesigned dashboard editor with more chart types, easier drag-and-drop layout, and dynamic dashboards. Classic Dashboards continue to work for orgs still on Classic but are no longer enhanced. New builds should use Lightning Dashboards.
Dashboard subscriptions
Salesforce supports email subscriptions for dashboards: schedule the dashboard to email a PDF or image to specific users on a cadence. The subscription respects dynamic dashboard settings; each recipient sees their own data scope.
How to build a Dashboard Widget
Building a widget takes three pieces: a source report, a widget type, and the configuration that maps report data to the visualization.
- Build the source report
A widget renders one report. Build the report first with the right groupings, filters, and columns to feed the visualization you want.
- Create or open the dashboard
From the Dashboards tab, New Dashboard (or open an existing one). Click Edit to enter the dashboard editor.
- Add the widget
Click Component or Widget. Pick the source report. Pick the widget type (bar, donut, metric, and others). Configure axis, color, sort, and any widget-specific options.
- Position and resize
Drag the widget into the dashboard layout. Resize as needed. Most dashboards have 4 to 12 widgets; fewer is usually better for cognitive load.
- Configure dashboard filters
Add up to three dashboard-level filters that propagate to every widget. Common filters: time range, region, business unit.
- Schedule a refresh and subscriptions
Set the refresh schedule and any email subscriptions. Save and activate the dashboard.
- Each widget pulls from one report only. Cross-report computations need a custom Lightning component or a pre-aggregated report type.
- Refresh is scheduled or manual, not real-time. Users sometimes expect data to be live; train them on the refresh cadence.
- Dashboards have a cap on widgets per dashboard (currently 20). For larger needs, split into multiple dashboards or use Tableau.
- Dynamic dashboards count against a per-org limit. Plan their use; do not make every dashboard dynamic.
- Widget formatting (colors, axes) is per widget; building dashboard-wide consistency requires manual effort or use of a shared template.
Trust & references
Cross-checked against the following references.
- Dashboards OverviewSalesforce Help
- Dashboard ComponentsSalesforce Help
Straight from the source - Salesforce's reference material on Dashboard Widget.
- Reports OverviewSalesforce Help
- Dashboard SubscriptionsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Dashboard Widget?
Q2. What widget type works well for single KPIs against a target?
Q3. What widget type works well when viewers need exact values?
Discussion
Loading discussion…