In most systems, everyone sees the same home screen. The manager and the warehouse supervisor encounter the exact same charts, and both have to hunt for what is useful to them.
The result is a screen that nobody really uses. After a while, the screen is bypassed, and everyone goes straight to their own report.
In this article, we explain role-based dashboard design, widget selection, layout logic, and data scope.
Table of Contents
Why role-based?
The value of a dashboard is measured not by the amount of data it displays, but by the decisions it drives.
A warehouse supervisor looking at a revenue chart generates no decisions; what they need is the pending shipments list.
Similarly, a manager does not need to check the shelf occupancy rate every day; they require higher-level indicators.
Therefore, the dashboard must vary according to the role, and each user must see what is relevant to their work.
We covered the role structure in the role-based authorization article.
Widget selection
The most common mistake in widget selection is putting every possible indicator on the screen.
A crowded screen causes no metric to be noticed and disperses attention.
The right approach is to select five or six metrics for each role. This number produces a screen that can be read at a glance.
The selection criterion is simple: does this metric produce a decision or action today?
If the answer is no, that metric should be in a report, not on the dashboard.
Layout
The position on the screen directly affects the probability of a metric being noticed.
The most critical metrics should be located in the upper section and on the left; the eye goes there first.
Alerts requiring action must also be at the top; a warning left at the bottom will go unseen.
Trend charts can be located in the lower section; these are for periodic review, not daily.
If a dashboard requires scrolling, the lower part is practically an unused screen.
Data scope
Each widget should display data according to the user's authorization scope.
A branch manager should see their own branch's turnover, not the total of the entire company. Otherwise, it is both unnecessary and misleading.
A sales representative should also only see the figures for their own portfolio.
This scope should be automatically derived from the authorization structure; it should not require a separate definition.
Sensitive metrics, on the other hand, should only appear in authorized roles; margin information is a typical example of this.
Role-based examples
The needs of different roles are seen more clearly with concrete examples.
For a warehouse manager, pending shipments, critical stock, and incoming goods receipt are the three most valuable metrics.
For a sales representative, open offers, due collections, and today's visit list stand out.
For accounting, pending documents, incoming e-invoices, and overdue receivables lists are meaningful.
For an executive, the turnover, collection, open order, and critical stock summary are sufficient.
Actionable metrics
A good widget doesn't just provide information; when clicked, it takes you to the relevant screen.
A user who sees the number of pending shipments should be able to reach that list with a single click.
When this connection is not established, the user has to search the menu separately for the number they see.
Indicators that do not require action are purely informational and should take up less space.
This distinction ensures that the screen transforms into a truly utilized tool.
Data freshness
How up-to-date an indicator is determines whether it can be trusted.
Real-time updated indicators and daily calculated ones must be distinguishable.
Displaying the last update time on the widget eliminates this ambiguity.
Heavy calculations should not be performed instantly; the loading speed of the screen directly affects usability.
A slowly loading dashboard quickly turns into an abandoned screen.
Personal customization
On top of the role-based default layout, users can be given limited customization options.
Changing the widget order or hiding some of them allows the user to build their own layout.
However, indicators outside the scope of authorization must not be added; customization should not exceed permissions.
A reset-to-default option must also be available; the user should be able to revert when they mess up their layout.
Excessive customization options, on the other hand, generate support overhead and weaken the common language.
Measuring usage
Whether the dashboard is working can be understood through usage data.
Widgets that are never clicked indicate that the metric is unnecessary and can be removed.
Directly asking users is also an effective method; which numbers they look at provides a clear answer.
The screen needs to be periodically reviewed; needs change over time.
For the executive set, daily KPI set you can check out the article.
Points to consider
Filling the screen with every possible indicator is the most common and most harmful mistake.
Indicators that do not generate actions also clutter the screen unnecessarily and distract attention.
A dashboard that loads slowly never becomes a habit.
Neglecting permission scopes creates both security risks and the risk of misinterpretation.
Screens are managed in the dashboard module.
Frequently asked questions
How many widgets are appropriate?
Five or six indicators per role are ideal for an at-a-glance readable screen.
Can the user modify their own screen?
Limited customization can be granted; however, permissions cannot be exceeded.
Are indicators calculated in real time?
Heavy calculations are performed periodically; freshness information should be displayed on the widget.
Is the same screen visible on mobile?
A simpler set is recommended for mobile; see the mobile dashboard article.
When set up correctly, a dashboard is a tool that guides the first five minutes of the day. When set up incorrectly, it is just a splash screen nobody looks at.
Choose a small number of indicators for each role; on a crowded screen, no indicator stands out.
Keep the selection criteria clear as well: does this indicator produce an action today? If not, its place is in a report.
Make widgets clickable; the user who sees the number should be able to reach the relevant list in a single step.
Do not neglect loading speed either; a screen that opens slowly never turns into a habit.
Review the screen periodically; widgets that are never clicked clearly show that the indicator is unnecessary.
Do not hesitate to ask users directly; which numbers they actually look at can provide clearer answers than usage data.
by contacting the EQLEM teamYou can plan your dashboard setup.