Skip to content
Tutorials Center
My learning

Topics

Lesson 26 of 36 ยท Reports and Dashboards

Salesforce Dashboards, Components and Running Users

Design Salesforce dashboards: components and chart types, source reports, dashboard filters, the running user and dynamic dashboards, refresh and subscriptions, with JavaScript stand-ins.

A dashboard is a page of charts and tables, each built from a report, that shows the state of the business at a glance. A sales leader opens one dashboard to see pipeline by stage, closed revenue against quota and the biggest open deals. Where a report answers a detailed question, a dashboard tells a story in a few seconds. Good dashboards are designed backwards from the decisions they support, and they depend on well-built source reports.

This lesson covers components, chart choice, dashboard filters, the running user (the setting that most often surprises new admins), refresh and subscriptions. The Salesforce screens are described in words; the code is a labelled JavaScript stand-in, not Salesforce.

Components and their source reports

Every dashboard component reads from one source report (a summary, matrix or joined report with groupings, or a tabular report for tables and metrics). Add a component with + Component, choose the report, then choose the type:

Component Shows Good for
Bar and column charts Values by group (horizontal or vertical, stacked or grouped) Comparing categories: pipeline by stage
Line chart Values over time Trends: new leads per month
Donut / pie Parts of a whole A few categories only
Funnel Steps that narrow Lead to Closed Won conversion
Scatter Two measures per point Deal size against age
Gauge One value against ranges Quota attainment
Metric One big number Open cases right now
Table The top rows of a report "Top 10 open opportunities"

A report's chart settings and a component are separate: a component picks its own chart type, groupings (limited to the report's groupings) and display units (record count, sum of a field, and so on). You can set the sort order, the number of groups shown, axis range, colors, and a title and subtitle. Show values and drill down (click a bar to open the report filtered to that group) are on by default.

Choose the chart by the question. Comparing values: bars. Change over time: a line. A share of a total: a donut with at most four or five slices. Avoid decorating a dashboard with many gauges and 3D effects; clear beats busy.

Dashboard filters

Dashboard filters let viewers slice the whole dashboard (by Owner, Region, Product or any field in the source reports) without editing it. An admin adds up to three filters, picking a field for each and the values to offer. Every component whose report contains (or can map to) that field is filtered; others ignore it. The filter field must exist on all the reports you want filtered, so a consistent set of report types makes filters work across components.

The running user

The most important dashboard setting is who the dashboard runs as. A dashboard is a snapshot of what the running user can see, and everyone who opens it sees those results, not their own data. There are three options:

  1. Run as a specified user: everyone sees what that user (often a manager or an integration-style user) can see. Good for an executive wall board, but dangerous: viewers see data they could not open in the reports.
  2. Run as the logged-in user (the dashboard is dynamic): each person sees only the data they have access to, so one dashboard serves the whole team. Dynamic dashboards have a limit on how many each org can have, and cannot be scheduled for refresh, so they refresh when opened.
  3. Let dashboard viewers choose whom to view the dashboard as: users with the right permission can switch the view to another user within their hierarchy.

A dashboard with a fixed running user can expose data to people without access to the underlying records. Before you pick a high-access running user, check who can see the dashboard, and keep the dashboard's folder sharing tight.

Refresh and subscriptions

A dashboard shows the data as of its last refresh. Viewers click Refresh, and admins can set a schedule (daily, weekly or monthly, at a time) so the data is ready when people arrive. Users can subscribe to receive an email with a dashboard snapshot on a schedule, and with a conditional rule (Send when a metric crosses a threshold, for example, open critical cases above 10). Limits apply to the numbers of scheduled refreshes and subscriptions per user, which vary by edition.

Design for understanding

  • Put the most important component at the top left; people read in that order.
  • Give a dashboard a purpose and an audience: "Support Manager: Daily Queue Health".
  • Limit a dashboard to a handful of components (a dashboard can hold up to 20, but fewer reads better).
  • Use consistent colors for the same thing (for example, Closed Won always green).
  • Use a header component (a metric or table) for the number everyone asks about.
  • Add a description to each component so viewers know what the filter and the date range are.
  • Keep source reports tight and fast: a slow report makes a slow dashboard. See Filters, buckets and formulas.
flowchart LR
  R1["Report: Open Pipeline by Stage"] --> C1["Funnel component"]
  R2["Report: Closed Won by Month"] --> C2["Line component"]
  R3["Report: Top Open Deals"] --> C3["Table component"]
  C1 --> D["Dashboard (filters: Owner, Region)"]
  C2 --> D
  C3 --> D
  U["Running user"] -.->|"decides which records are included"| D

Each component has its own source report; the running user decides which records the whole dashboard can see.

Stand-in: the running user changes the numbers

This stand-in is not Salesforce. It shows why the same dashboard shows different totals depending on whose access it runs with.

JS Stand-in: dashboard totals by running user

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Stand-in: choosing the right number of slices

JS Stand-in: roll small groups into Other

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Folders and access

Dashboards live in folders with their own sharing: viewer, editor or manager access for users, roles and groups. A dashboard also needs access to its source reports, because a viewer who cannot access the report folder still sees the component (it uses the running user's access), but cannot drill into it. Keep reports and dashboards for one team together, and see Sharing, folders and report limits.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A dashboard runs as the CEO and is viewed by sales reps. What do the reps see?

    A fixed running user determines the data for everyone who opens the dashboard.
  2. 2. What is a dynamic dashboard?

    Dynamic dashboards run as the viewing user.
  3. 3. How many dashboard filters can an admin add?

    A dashboard supports up to three filters.
  4. 4. Which component best shows one number such as open cases right now?

    A metric component displays a single large value.

Summary

  • A dashboard is a set of components, each driven by a source report, with up to three filters.
  • Pick chart types for the question: bars to compare, lines for trends, donuts for a few parts, a metric for one number.
  • The running user decides which records everyone sees; use dynamic dashboards or tight folder sharing to avoid exposing data.
  • Schedule refreshes and subscriptions so the right people get current numbers.

Next: Sharing, folders and report limits