How to Build Salesforce Dashboards Managers Actually Read
Admins often build dashboards for the screen: twenty components, careful colors, filters for every team. Then the manager who asked for it never logs in to look. Many managers see dashboards the way Salesforce delivers them when they are busy: as a scheduled email.
This guide shows how to design for that reader, using what Salesforce documents about dashboard subscriptions, running users and limits.
Start with how the dashboard will be delivered
Salesforce lets you "subscribe yourself and other users, groups, or roles to receive refreshed dashboard results by email on a schedule that you set." If your manager asked for "a weekly view of the pipeline", the real request is often an email on Monday morning.
Before you build anything, ask the requester three questions:
- Will you open it in Salesforce or read it in your email?
- How often do you need it? Daily, weekly or monthly.
- What decision will you make from it? One clear decision usually means fewer components.
Choose the running user deliberately
When people receive a dashboard by subscription, Salesforce states that "recipients see the same report data as the person running the report." It adds that "it is possible that they see more or less data than they normally see in Salesforce."
That makes the running user a real decision:
| Running user choice | What recipients see | Watch out for |
|---|---|---|
| A senior user or admin | Everything that user can see | Recipients may see data they normally cannot |
| The recipient's own level | Data close to what they see in Salesforce | The dashboard may look different for each team |
| Dynamic dashboard (runs as the viewer) | Each viewer's own data | Limited number per org (see below) |
Rule of thumb: before adding a subscriber, check that they are allowed to see everything the running user can see.
Respect the limits early
Salesforce documents several limits that shape dashboard design. Check your own edition, but as Salesforce lists them:
- Subscriptions per user: "Each user in an Unlimited Edition org can subscribe to up to 15 reports and 15 dashboards. Users in other orgs can subscribe to up to 7 reports and 7 dashboards."
- Filters: up to 5 filters on a dashboard, with up to 50 values in a single filter.
- Components: a maximum of 20 charts and tables on a dashboard.
- Dynamic dashboards per org: up to 3 in Developer Edition, up to 5 in Enterprise Edition and up to 10 in Unlimited and Performance Editions.
Because subscriptions are limited per user, it is better to build one dashboard a manager will actually read than five they will not.
Design for the inbox
A layout that works in an email is simple:
- Put the answer first. The top-left component should answer the main question, such as "Open pipeline this quarter".
- Use fewer components. Four to six clear charts are easier to scan than twenty.
- Title each component as a sentence. "Deals closing this month by stage" is clearer than "Opp Chart 3".
- Avoid relying on filters. A reader in email will not change a filter, so build the view they need by default.
- Pick one time period and say it in the dashboard name, such as "Pipeline, this quarter".
A simple build process
- Write the requester's decision in one sentence.
- Sketch four to six components on paper that answer it.
- Choose the running user and check who will receive it.
- Build the reports, then the dashboard.
- Subscribe yourself first and read the email on your phone.
- Adjust, then add the requester as a subscriber.
Practice it in a free org
In a free Developer Edition org, build a small dashboard from sample data, subscribe yourself, and look at the email you receive. Seeing the gap between the screen and the inbox is the fastest way to learn this. It also makes a good portfolio project to talk about in interviews.
Related reading
- What does a Salesforce admin actually do all day?: reporting is a large part of the job.
- Should you learn Tableau or CRM Analytics?: for when standard dashboards are not enough.
- Our Substack post They Will Read It as an Email covers the same idea in a short read.
Frequently asked questions
How do I send a Salesforce dashboard by email? Subscribe users, groups or roles to the dashboard and set a schedule. Recipients receive the refreshed results by email.
What data do subscribers see? The same data as the dashboard's running user, which can be more or less than they normally see in Salesforce.
How many dashboards can a user subscribe to? Up to 15 in Unlimited Edition and up to 7 in other editions, according to Salesforce's limits page.
How many components should a dashboard have? Salesforce allows up to 20, but for a manager reading in email, four to six focused components usually work better.
Blazer2Role helps career changers move into Salesforce roles, and we sell coaching and courses. Limits and features vary by edition and change over time, so check current Salesforce documentation for your org. Drafted with AI assistance under Blazer2Role's editorial direction.