# A Salesforce dashboard for a sales manager: six components, one question each

https://salesbond.app/blog/salesforce-dashboard-sales-manager-components/
Published: 2026-10-15 · Updated: 2026-10-26

A Salesforce dashboard is a page of charts, tables and metrics, each one fed by a report. For a sales manager the useful version has five or six components, and every component passes the same test: there is one question you ask about it on Friday, and one field the reps actually fill in that makes the answer true. A component that fails either half of that test is decoration, and decoration is what gets a dashboard ignored.

## A dashboard nobody opened on Friday

Daniel inherited a dashboard called “Sales Overview” with fourteen components on it: a funnel, two gauges, a donut of lead sources, a leaderboard, and a table at the bottom nobody had scrolled to since it was built. The colours matched. He opened it on his first Friday and closed it within a minute, because nothing on the page told him what to do before Monday. By the third week he was running the review from a filtered list view and a notebook.

We think this is the normal fate of a dashboard built from “what can we show” instead of “what do I need to ask”. Salesforce makes the first kind very easy to build. The second kind takes about an hour and a willingness to delete things. For the rest of the product, see [Salesforce Sales Cloud for a small sales team](https://salesbond.app/blog/salesforce-sales-cloud-manager-weekly-use/).

## Salesforce report vs dashboard: what each is for

A report answers one question with rows: which opportunities, grouped how, summed by what. A dashboard puts several of those answers on one page, and Trailhead is precise about where the numbers come from: each widget “shows rich text, an image, or data from one report” ( [Trailhead: Visualize Your Data with the Lightning Dashboard Builder](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data)).

So a dashboard has no data of its own. Every number on it carries the source report’s filters and blind spots, and if a component looks odd, you open its report. The honest order of work follows from that: a short list of questions, one report per question, then a page that puts the uncomfortable number where the eye lands first.

## Building it: four clicks that matter

The clicks are in Trailhead’s dashboard builder module; these are the four that decide whether the page is any use.

1. Dashboards tab, then **New Dashboard**.
2. **\+ Widget**, then pick the source report for each component.
3. **\+ Filter** on Opportunity Owner, so one page narrows to one rep.
4. **Properties**, then **View Dashboard As**: a named user, or the viewer.

Step 4 is the one that causes arguments later, so it gets its own section below. The reports behind the first three components, with their filters, are in [the Salesforce reports a manager opens on Monday](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/); we don’t repeat the build here.

## Six Salesforce dashboard components worth keeping

Each entry is a component, the Friday question it answers, and the field that keeps it honest. The order on the page is the order below: the first thing a manager should see is the thing that already went wrong.

![Wireframe of a five-component sales dashboard: two tables, a bar chart, a single metric and a stacked bar, each with one question](https://salesbond.app/wp-content/uploads/2026/10/salesforce-dashboard-sales-manager-components-2.png)

1. Slipped close dates. Question: what did we say would close and didn’t, and what is the new date? Field: Close Date, which reps update when a deal moves and quietly don’t when it stalls.
2. Gone quiet. Question: who stopped working their deals, or whose buyer stopped answering? Field: last activity, which is only as true as the logging behind it.
3. Open pipeline by stage and owner. Question: where does the open money sit, and did it move since last Friday? Field: Stage. Read it for movement, not size.
4. Closing this month. Open opportunities with a Close Date inside the current month, grouped by stage. Question: what has to become true in the next few weeks for the month to land, and is the Stage plausible for that date? A deal in an early stage with a close date next Tuesday is either a mistake or a story worth hearing.
5. Won and lost this quarter by owner. Two numbers per person, not a leaderboard with a crown. Question: who is converting what they work, and whose lost column is filling faster than anyone mentioned? Source: a closed opportunities report filtered to the quarter, grouped by owner and by won or lost.
6. Missing Next Step. A single metric component: the count of open opportunities where Next Step is blank. Question: how much of this pipeline is anyone’s plan? If the count is large, components 1 through 5 are built on guesses, and the Friday review should start here. Source: an open opportunities report with one filter, Next Step equals blank.

That is the whole page. No funnel, no lead sources, no activity-by-type bar. Those are real questions for someone, usually marketing or ops, and they belong on that someone’s dashboard. For the CRM-neutral version of which numbers a manager should watch at all, see [the sales manager dashboard: six numbers](https://salesbond.app/blog/sales-manager-dashboard-six-numbers/); this article is only the Salesforce build.

## Why your number differs from mine

The call we hear most often goes like this. The manager opens the team dashboard and reads a pipeline figure. The rep opens the report behind that component, or a copy of the dashboard he saved for himself, and gets a smaller figure. Twenty minutes go to the question of who is right, and the answer is both.

Start with the running user: the user whose access decides what data a dashboard shows. You set it in View Dashboard As, and when it is a named person, “when people open your dashboard, they see data as the person that you specified” ( [Trailhead: Visualize Your Data with the Lightning Dashboard Builder](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data)). So on one dashboard with a fixed running user, the manager and the rep see the same number. If an admin built it and left themselves as running user, everyone sees the admin’s view, which is usually everything.

The gap appears somewhere else. The rep’s report, opened directly, shows him his own access rather than the running user’s. His copy of the dashboard may have a different running user. Or the two of them simply have different values selected in the dashboard filter: in our builds, a filter such as Owner or Region narrows what the source reports already return, and two people on “the same dashboard” with different filter values will never agree.

Before you argue about a number, ask four things in order: is it the same dashboard or a report, who is the running user, what is the dashboard filter set to, and what filters does the source report carry. In our experience one of those settles it nearly every time, and the data itself is rarely the problem.

Our view: a management dashboard should run as the manager, not as whoever built it. Then the figure on the page is the figure the manager is accountable for.

## Dynamic dashboards: one layout, many views

A dynamic dashboard runs as whoever opens it. In the properties you set View Dashboard As to “The dashboard viewer”. Trailhead’s worked example is a manager who would otherwise maintain 45 dashboards and ends up with two, and in that setup “all users see only data that they can access” ( [Trailhead: Visualize Your Data with the Lightning Dashboard Builder](https://trailhead.salesforce.com/content/learn/modules/lex_implementation_reports_dashboards/lex_implementation_reports_dashboards_visualizing_data)).

For the six components above this is the sane default. A rep opening it sees their own slipped deals and their own blank Next Steps; the manager sees the team’s. One page, one set of reports to maintain, and its fine that the numbers differ, because now everyone knows why.

There is a second option, “Let dashboard viewers choose whom they view the dashboard as”. With View My Team’s Dashboards or View All Data, a manager can flip the page to one rep’s view during a one-to-one without building anything (same module). The folder rule for dynamic dashboards is in [the reports piece](https://salesbond.app/blog/salesforce-reports-sales-manager-weekly/), and check your edition’s documentation before you plan a dozen of them. One per manager is usually plenty.

## Check the dashboard against the deals

A dashboard you have not tested against real deals is a hypothesis. Here is the test we run before trusting one and it takes under an hour.

Pick ten open opportunities by hand. Not the ten biggest; a mix: two you know are stuck, two that closed late last quarter and got re-dated, two from the rep you trust most, two from the rep you worry about, and two at random from the list view. Write down, for each, what you believe: is it quiet, is its close date already past, is there a Next Step, which stage is it in.

Now open the dashboard as yourself and find each of the ten. Every opportunity should appear exactly where your notes say, and nowhere else. A deal you know is stuck but which is missing from Gone quiet usually means the rep logged a task with no real contact, or your activity threshold is too generous. A deal in Closing this month that you had mentally written off tells you Stage and Close Date are being edited by different people with different stories.

A made-up but typical result: of ten deals, seven land where expected, two show the activity threshold is wrong, and one reveals a report filter on record type that excludes a whole product line. The numbers are illustrative; the pattern is what you are looking for. Fix the reports, not the dashboard, then run the ten again.

Repeat the check once a quarter, or any time a rep says the dashboard is “wrong about me”. Occasionally they are right, and that is the cheapest audit you will get. If the mismatches cluster around one owner, the next step is [a Salesforce opportunity audit](https://salesbond.app/blog/salesforce-opportunity-audit-sales-manager/) of that pipeline. If your org uses Pipeline Inspection, we wrote about [when to use it for the weekly review](https://salesbond.app/blog/salesforce-pipeline-inspection-weekly-review/) separately.

## What stays on the page after a year

The dashboards that survive are boring. Six components, each with a question the manager actually asks, running as the manager or as the viewer, checked against ten real deals when it was built and whenever someone doubts it. People open them because the top-left table has three rows in it and one of them is a surprise.

That hand check is the part we got tired of doing ourselves. We build SalesBond, a sales management layer on top of the CRM a team already uses, Salesforce included. Deal Health reads the same fields the six components depend on, Close Date, Next Step, last activity, Stage, and checks every open opportunity against more than 20 rules, so “is it quiet, has it slipped, is there a plan” is answered per deal on the Sales Dashboard without rebuilding reports or arguing about the running user. [Check your CRM with SalesBond](https://salesbond.app/).

Either way delete the funnel. Daniel did, and his team started opening the page.