Customize Dashboards
Create dashboards and arrange widgets for the way your team works.
Use custom dashboards when different teams need different operating views. A sales team may care about deals and follow-ups, while an owner may care about revenue, open invoices, bookings, and overdue work.
A useful dashboard has a clear audience. If the audience cannot act on the widgets, create a different dashboard or remove the widget.
Treat each dashboard as a working view for a specific job, not as a place to put every metric the workspace can show.
Create a Dashboard
Open the dashboard area, create a dashboard, give it a clear name, and add the widgets that match the purpose of the view. You can start from a blank dashboard or from a sales, finance, operations, or leadership template.
Use names that tell users when to open the dashboard, such as "Daily Sales Review", "Finance Collections", or "Delivery Operations".
Before adding widgets, write down the questions the dashboard should answer. For example: Which deals need attention? Which invoices need follow-up? Which projects are at risk? This prevents a dashboard from becoming a loose collection of unrelated widgets.
Arrange Widgets
Put the most urgent information near the top. Keep related widgets close together so the page is easy to scan. Save the layout before leaving edit mode.
After arranging widgets, refresh the page and confirm the saved layout still matches what you intended. Then open the dashboard with a non-owner role if the view will be shared with teammates.
Keep stable dimensions in mind when mixing tables, charts, and stat cards. Large charts belong below the key decision widgets; small stat cards work best in groups where the labels and numbers can be scanned quickly.
When to Create a Separate Dashboard
Create a separate dashboard when the audience or job is different:
- Owner overview
- Sales pipeline
- Finance review
- Delivery operations
- Team workload
- HR overview
Keep Dashboards Useful
Review dashboards after process changes, new modules, new reports, or role changes. Remove stale widgets and rename dashboards that no longer match their purpose.
If a widget looks empty, check the related module, permissions, date range, and record status before deleting it.
Dashboard Ownership
Assign an owner to each shared dashboard. The owner is responsible for updating widgets after process changes, removing stale metrics, and deciding whether the dashboard still supports a real operating review.
When no one owns a dashboard, users may keep trusting old numbers because the layout still looks polished. Review unused dashboards and archive or rename them before they become misleading.
Dashboard Design Review
Before sharing a dashboard:
- Confirm the audience.
- Confirm the decisions it supports.
- Put action-oriented widgets first.
- Remove duplicate or vanity metrics.
- Test with a non-owner role if others will use it.
Create a simple review habit: owner dashboards monthly, finance dashboards before billing review, sales dashboards before pipeline meetings, and delivery dashboards before project reviews. Retire dashboards that no one uses so users do not rely on outdated numbers.
Troubleshoot A Custom Dashboard
If users see different data, compare role permissions, module access, widget filters, saved layout, and active workspace. If layout changes do not stick, save again, refresh, and confirm you are editing the correct dashboard rather than a template or different workspace view.