Dashboard
A Dashboard is a Salesforce analytics surface that displays multiple report results as visual components (charts, gauges, metrics, tables) on a single page.
Definition
A Dashboard is a Salesforce analytics surface that displays multiple report results as visual components (charts, gauges, metrics, tables) on a single page. Each dashboard component pulls from one underlying report, applies an aggregation or visualization, and renders inside the dashboard layout. Dashboards refresh on a schedule or on demand, and the rendered state caches until the next refresh, so consumers see consistent numbers without re-running reports manually.
Dashboards are the executive and operator face of Salesforce data. Sales pipelines, support backlogs, marketing attribution, finance close progress, partner health: each is typically a dashboard with five to twenty components arranged for at-a-glance reading. Lightning dashboards support twenty components per dashboard, with filters at the dashboard level that cascade to every component. Each component has a running user, which determines the data context used to evaluate the source report; this is the mechanism that lets one dashboard serve different audiences based on whose access drives the data.
How dashboards turn Salesforce reports into operational surfaces
Components and supported visualization types
Each dashboard component references one source report and renders the data as a chart, gauge, metric, or table. Chart types include bar (horizontal and vertical), column, donut, funnel, line, scatter, and stacked. Gauges visualize a single value against thresholds. Metrics show one number with optional comparison. Tables display tabular report output directly. Choose the visualization that matches the data shape: time series fits line and column, distribution fits donut, KPI tracking fits metric or gauge. Mismatched visualization choices are the most common source of dashboard rework.
Running user and the data context model
Each dashboard has a running user setting that determines whose data access drives the report queries. Run as Specified User shows everyone the same data based on that user's access (typical for executive dashboards). Run as Logged-In User shows each user their own slice (typical for personal pipelines or rep-level dashboards). Run as Dashboard Viewer (introduced in 2020) gives the consumer control while still using the underlying report definitions. The running user choice has huge implications for both data sensitivity and dashboard reusability across teams.
Filters that cascade to every component
Dashboard filters appear at the top of the dashboard and cascade to every component that uses the filtered field. Filter by close date range, opportunity stage, region, product family. Each filter offers up to ten predefined values (Last Quarter, Current Quarter, Next Quarter for date filters). Filters change the data displayed without modifying the underlying reports. This is the mechanism that lets one dashboard serve as a quarterly business review template by changing the filter rather than rebuilding the dashboard each quarter.
Refresh schedules and dashboard subscriptions
Dashboards do not refresh automatically every time someone views them. The rendered state caches and shows the last refreshed values. Schedule daily, weekly, or monthly refresh windows via Setup or via the dashboard subscribe button. Users can also subscribe to receive refreshed dashboard images via email, useful for executives who want a Monday-morning view without clicking into Salesforce. Refresh runs as the running user, which means caching the right user's data context is part of the schedule design.
Lightning dashboards versus Classic dashboards
Lightning Experience introduced a redesigned dashboard builder with more chart types, drag-and-drop layout, and 20 components per dashboard (up from Classic's 3 columns of 20 components). Lightning dashboards also support dashboard tables that display tabular report data and the dashboard filter framework that replaced the older custom filter pattern. New dashboards should be built in Lightning. Classic dashboards still render but migration is a one-way conversion that loses some Classic-specific behaviors.
Dynamic dashboards and personalization
Dynamic dashboards (now called Run as Logged-In User dashboards) personalize the data per viewer. The same dashboard shows different numbers to different users based on their own Salesforce data access. This is the right pattern for rep-facing pipeline dashboards where each rep should see only their own deals. Each org has a limit on dynamic dashboards (5, 10, or 20 depending on edition), so plan their use carefully. Static-running-user dashboards have no such limit.
Performance and large data volumes
Dashboards perform well when source reports are selective and aggregate efficiently. Reports that scan millions of rows produce slow component rendering and can hit report timeout limits. The mitigation: use report filters on indexed fields, limit row count with LIMIT clauses, lean on aggregate functions instead of detail rows. For very large data, consider CRM Analytics (formerly Tableau CRM, formerly Einstein Analytics) which is built for analytical workloads at scale and integrates with standard Salesforce dashboards.
How to build a Dashboard
Building a useful dashboard takes more thought than dragging chart components onto a canvas. Plan the audience, the questions the dashboard answers, the underlying reports, and the filters before opening the builder. The best dashboards answer three to five specific questions cleanly rather than displaying everything you could possibly visualize.
- Identify the audience and the questions
List the people who will read the dashboard and the questions they are trying to answer. Sales VP looking at quarterly pipeline. Support manager tracking Case SLA. Marketing director measuring campaign ROI. Each audience needs different metrics and different time windows.
- Build the source reports first
Each dashboard component needs a source report. Build the reports before the dashboard. Confirm each report runs in under a few seconds with realistic data volumes. Slow reports produce slow dashboards.
- Create the dashboard
App Launcher > Dashboards > New Dashboard. Pick a folder for storage. Enter the dashboard label and description. The dashboard opens in the Lightning Dashboard Builder.
- Add components from the source reports
Drag the Component tile onto the canvas. Pick the source report, the visualization type, and any visualization-specific settings. The component preview updates live as you configure. Repeat for each metric you want to display.
- Set the running user
Dashboard Properties > Running User. Choose Specified User for executive dashboards where everyone sees the same data. Choose Logged-In User (dynamic) for personalized dashboards where each user sees their own slice.
- Add dashboard filters for time windows and segments
Dashboard Properties > Filters > Add Filter. Configure up to three filters per dashboard. Common filters: Close Date Range, Stage, Owner, Account Industry. Each filter cascades to every component that uses the filtered field.
- Schedule refresh and configure subscriptions
Dashboard > Subscribe button. Set refresh frequency (daily, weekly, monthly) and notification recipients. Schedule refresh during off-peak hours if the source reports scan large data sets.
- Share the dashboard folder
Dashboard Folder > Share > add users, groups, or roles with View or Manage access. Folder-level sharing controls who can see and modify the dashboard. Confirm permissions match the intended audience before announcing the dashboard.
Specified User for shared data context. Logged-In User for personalized per-viewer data. Dashboard Viewer for hybrid control.
Chart (bar, column, donut, line), gauge, metric, table. Pick to match the data shape and the question being answered.
Up to three filters that cascade to every component. Common patterns: time range, owner, segment, region.
- Dashboards do not auto-refresh when viewed. The rendered state caches until the next scheduled or manual refresh. Users seeing stale numbers is the leading dashboard support ticket.
- Running user choice has security implications. Specified User dashboards expose that user''s data access to every viewer; Logged-In User dashboards personalize but consume from the dynamic dashboard limit.
- Source reports that scan large data volumes can produce slow dashboard rendering or hit report timeout limits. Build selective reports first, then the dashboard.
- Lightning dashboards support 20 components max. Beyond that, build a second dashboard. Cramming too many components into one degrades readability and slows the load.
- Folder sharing controls dashboard visibility. Saving a dashboard to the wrong folder either hides it from the intended audience or exposes it to people who should not see it.
Trust & references
Cross-checked against the following references.
- Dashboards OverviewSalesforce Help
- Create a DashboardSalesforce Help
- Dashboard Running UserSalesforce Help
Straight from the source - Salesforce's reference material on Dashboard.
- Create a DashboardSalesforce Help
- Filter DashboardsSalesforce Help
- Subscribe to DashboardsSalesforce 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 type of data does Dashboard typically work with?
Q2. What is the primary purpose of Dashboard in Salesforce?
Q3. Who benefits most from Dashboard in an organization?
Discussion
Loading discussion…