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.
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. Each widget reads data from a single source report and renders it as a chart, gauge, metric, or table. A dashboard is a layout of several widgets that share filters and refresh together. Each widget is configured on its own.
Dashboard Widgets exist to make report data faster to read than the underlying tabular report. One widget condenses a report into a bar chart, donut, metric tile, or summary table that a leader can scan in seconds. Salesforce ships a fixed set of widget types. The dashboard editor is drag and drop, and building a widget means picking a source report, choosing a display type, then setting axis, grouping, and sort options.
How a Dashboard Widget turns a report into a tile
Every widget points at one source report
A Dashboard Widget never holds its own data. It points at exactly one source report, and that report does the querying. When you add a widget, the dashboard editor asks you to pick the source report first. The rendering layer then reads the report rows, applies the widget settings (display type, groupings, sort, top N), and draws the tile. Any change you make to the source report flows through. Edit the report filter, add a column, or change the grouping, and the widget reflects it on the next refresh. This one report per widget rule is the single most important thing to understand. It explains why a widget cannot blend values from two reports, and why a dashboard that needs five different views needs at least five reports behind it. The report must also live in a folder the dashboard running user can open. If the report is deleted or moved out of reach, the widget breaks. Building a clean dashboard therefore starts with building clean, well-scoped reports first.
The widget types and what each answers
Salesforce gives you a fixed menu of display types, and each one answers a different question. Bar and column charts compare a value across categories, like pipeline by stage. Line charts show a measure over time, which suits trend questions. Donut and pie charts show parts of a whole. Funnel charts show an ordered drop off, such as a sales pipeline. Scatter charts plot two measures against each other. Gauge charts show progress toward a target, with green, yellow, and red segments you define. Metric components surface one headline number, like total closed revenue. Tables list the actual rows when the data does not summarize cleanly, and a Lightning table can show up to 200 records. There is also a Lightning component widget that hosts a custom Lightning Web Component for interactive or external visuals. Pick by intent, not by looks. If the leader asks how am I tracking to goal, use a gauge. If they ask what is the trend, use a line. The wrong type hides the answer in plain sight.
Dashboard filters override the source reports
A dashboard can carry up to five filters, and each filter holds up to 50 values. A filter is defined once on the dashboard and applies to every widget whose source report contains the filtered field. This matters because it lets one dashboard serve many slices without rebuilding reports. Add a Region filter, and a viewer can flip the whole dashboard from West to East with one picklist. The filter overrides the matching filter on each source report at view time. Widgets whose report lacks the field simply ignore that filter. Filters live at the dashboard level, so they are a property of the layout, not of any single widget. They pair well with subscriptions and with dynamic dashboards. A common pattern is one Sales Performance dashboard with a Quarter filter and a Region filter, cloned for no one, because the same dashboard now covers every quarter and territory. Plan the filter fields early, since a filter only works when the field exists on the underlying reports.
Static dashboards versus dynamic dashboards
By default a dashboard runs as a fixed running user, so every viewer sees the same numbers, scoped to that one person. A sales rep and a VP open the dashboard and read identical data. A dynamic dashboard instead runs as the logged in viewer. The data then scopes to whatever each person is allowed to see through sharing. One dynamic Team Pipeline dashboard can show each manager only their own team, with no cloning. The trade off is supply. Dynamic dashboards are capped per org by edition. Enterprise and Performance allow more than Group edition, and the exact number is in the limits documentation. Some products, such as Financial Services Cloud, grant extra dynamic dashboard licenses. Dynamic dashboards also cannot be scheduled to refresh automatically, and they ignore the As specified setting on the running user. Choose static when everyone should see the same authoritative figure, and choose dynamic when the answer should change per person. Mixing both styles across an org is normal and expected.
Refresh timing and the data lag trap
Dashboard Widgets do not show live data. They show a snapshot from the last refresh. A user can refresh manually with the Refresh button, or an admin can schedule the whole dashboard to refresh on a cadence, then optionally email the result. Until a refresh runs, every widget keeps displaying the previous values, with a timestamp showing how stale the data is. This surprises people who expect a dashboard to update the instant a deal closes. It does not. The lag is fine for an executive review that runs each morning, and risky for anything operational where minutes matter. There are caps on how many scheduled refreshes an org can run, so refreshing 200 dashboards every hour is not realistic. The practical move is to refresh on a schedule that matches the decision. Daily for leadership reviews, or a few times a day for an active sales floor. Tell viewers to read the as of timestamp, and to hit Refresh before they make a call on the numbers.
Lightning dashboards, Classic, and subscriptions
Lightning Experience ships a redesigned dashboard editor with more chart types, a flexible 12 column or 9 column grid, color themes, and dynamic dashboards. Classic dashboards still run for orgs on Salesforce Classic, but they are no longer being enhanced, so new builds belong in Lightning. A single dashboard can hold up to 25 widgets, with a combined cap on charts and tables, so a tight six to eight widget layout reads better than a crowded one anyway. Subscriptions close the loop on delivery. A user can subscribe to a Lightning dashboard and receive the refreshed result by email on a schedule, or schedule a refresh without the email. The subscription respects the running user, so a dynamic dashboard emails each recipient their own data scope. You can route the email through an org wide address by enabling that setting in Setup. Subscriptions turn a pull tool into a push tool, which matters because most managers will not log in daily to check a dashboard on their own.
How to add a widget to a Lightning dashboard
Add a widget to a Lightning Experience dashboard. You need the Run Reports and Create and Customize Dashboards permissions, and the source report must already exist in a folder the dashboard viewers can open.
- Open the dashboard in edit mode
From the Dashboards tab, open the dashboard and click Edit, or click New Dashboard to start fresh. The drag and drop editor opens with the existing widgets, if any.
- Add a widget and pick the source report
Click + Widget, then select the source report that holds the data. Each widget reads from exactly one report, so choose the report whose rows answer the question this tile should show.
- Choose the display type
Pick a chart, gauge, metric, or table. Use a bar chart to compare categories, a line chart for trends, a gauge for progress to a target, and a metric for one headline number.
- Configure axis, grouping, and sort
Set the X and Y values or the measure, choose groupings, set units and decimals, and pick a sort order. Optionally inherit chart settings from the report, then click Add.
- Arrange, set the running user, and save
Resize and position the widget on the grid. Under Properties, set View Dashboard As for static or dynamic behavior, then click Save and Done.
The single report that feeds the widget. It must exist and sit in a folder the running user can access.
The visual format: chart (bar, line, donut, funnel, scatter), gauge, metric, or table.
The value to plot and how to group it, such as Sum of Amount grouped by Stage.
A clear label so viewers know what the tile shows without opening the report.
- A widget reads one report only. To blend data from two reports, build a third report or use CRM Analytics instead.
- A dashboard filter only works on widgets whose source report contains the filtered field. Others ignore it silently.
- Widgets show last refresh data, not live data. Schedule a refresh that matches how the dashboard is used.
- Dynamic dashboards are capped per org by edition and cannot be scheduled to refresh automatically.
Prefer this walkthrough as its own page? How to Dashboard Widget in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Dashboard Widget.
- Dashboard Component TypesSalesforce
- Reports and Dashboards Limits and AllocationsSalesforce
Hands-on resources to go deeper on Dashboard Widget.
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 on a Salesforce dashboard?
Q2. What Dashboard Widget type works well for showing a single KPI against a target value?
Q3. What Dashboard Widget type works well when viewers need exact numeric values, not visuals?
Discussion
Loading discussion…