Dashboard Widgets
Understand what dashboard widgets show and why data may be missing.
Dashboard widgets summarize records from the workspace.
Use widgets to monitor the work you need to notice quickly, then open the underlying module when a number needs investigation.
Treat widgets as signals, not the final audit source. Use the widget to decide what to inspect, then open the relevant CRM, finance, productivity, HRM, or reporting page to take action.
Widget Categories
- General widgets summarize workspace stats, revenue trends, quick insights, and open tasks.
- CRM widgets summarize CRM stats, sales pipeline, recent activity, and active deals.
- Finance widgets summarize revenue, expenses, invoice activity, and collection attention.
- Projects widgets summarize project stats, timelines, team performance, and active projects.
- HRM widgets support employee clock in/out where attendance is enabled.
Widget Controls
When a dashboard is in edit mode, widgets can be moved, resized, duplicated, configured, or removed. Some widgets support period, group, and sort settings.
Configure widgets around the question they should answer. For example, a finance widget may be useful with a monthly period, while a task widget may be more useful when it focuses on open work.
Before changing a shared dashboard, check who uses it. A widget that helps an owner may distract a sales or delivery user, so create separate dashboards when the audience needs different decisions.
Choose High-Signal Widgets
Use widgets that lead to action. If nobody knows what to do when a widget changes, remove it or replace it with a more specific widget.
Missing Data
If a widget looks empty, check that the related module has records, your user has permission to view them, and the widget's time range or filter includes the data.
Also check whether the record status is included. Closed tasks, paid invoices, archived projects, or inactive deals may be intentionally excluded depending on the widget.
If only one user sees missing data, compare their role, module access, active workspace, and dashboard visibility. If everyone sees missing data, check the source records, widget configuration, and date range first.
Build A Useful Dashboard
Start with a few high-signal widgets instead of filling the dashboard with every available metric. A good operations dashboard usually combines:
- Work that needs attention now.
- Money that needs collection or review.
- Sales or support activity that is moving.
- Team workload or attendance signals when HRM is used.
Review dashboards after imports, workflow changes, finance setup changes, and role changes. Widgets are most useful when the underlying records are current and the viewer has permission to act on what they see.
After a dashboard review, open the source module for any surprising number and fix the underlying records there.
Review Cadence
Review dashboard widgets when the team changes process, imports data, updates permissions, or adds new modules. A dashboard that was useful during setup may be noisy once the team is operating normally.
If a widget repeatedly shows information no one acts on, replace it with a metric tied to a real review routine.
Remove Low-Signal Widgets
Keep widgets that help someone make a decision, follow up, collect money, resolve support, or rebalance work. Remove widgets that look interesting but do not change what the team does.
If a dashboard becomes crowded, keep the operational review widgets first and move occasional reporting questions into reports or saved views.