monday.com dashboards combine widgets, charts, numbers, timelines, battery-style progress bars, pulled from one board or several connected ones, into a single view a team checks instead of opening every board separately. Every number traces back to a value already sitting in a column somewhere. If the number that actually matters lives in your accounting system or your support desk instead, no dashboard widget can see it until it gets there first.
A dashboard is built by adding widgets and pointing each one at a board, a column, and a calculation, a sum, a count, an average, a status breakdown. Widgets can pull from multiple boards at once if they're connected, which is how most teams build a cross-project rollup without leaving monday.com.
The Activity Log, a separate feature from dashboards, tracks every change made to a board, who edited what and when, useful for auditing or catching an accidental edit after the fact rather than for ongoing reporting.
All of this reads from board data that's directly queryable through monday's API too, so if you need the same numbers somewhere other than a dashboard widget, a scheduled report, a BI tool, nothing's actually blocking that at the data level.
A dashboard widget can only sum, count, or average a value that's already a column on a monday.com board. True gross margin, fulfillment rate, support ticket volume, anything that only your accounting or help desk system knows, doesn't exist on the dashboard until someone syncs it onto a board first. The dashboard looks complete. It's just missing the half of the picture that never made it into monday.com.
The fix isn't a different widget. It's getting the number from wherever it actually lives onto a board column the dashboard can already see, which is a sync problem, not a reporting-feature problem.
Margin, fulfillment status, or any number that lives outside monday.com gets synced onto a board as its own column, so the dashboard your team checks every Monday isn't missing the half that actually matters.
When the boards a true company-wide number depends on were never set up as connected boards, we pull the underlying data through the API and build the rollup dashboards can't natively assemble on their own.
If it exists somewhere outside monday.com and never makes it onto a board, that's a sync problem worth fixing, not a limit you have to live with.
Tell us which figure never makes it onto a monday.com board, margin, fulfillment, support load, whatever it is. We'll scope what it takes to get it there automatically. Dashboards are one example; n-frames fixes this same gap wherever a number is trapped in a system that doesn't talk to the one your team actually checks.
Let's talk →Yes, as long as those boards are set up as connected boards first. A widget can then pull and roll up values across all of them into a single number or chart.
It's an audit trail of every change made to a board, who edited which column and when. It's built for catching or reversing an unwanted edit, not for ongoing reporting the way dashboard widgets are.
Individual widgets and the underlying board data can be exported, though export depth and format options vary by plan tier. There's no single native export that hands you the whole assembled dashboard as a file.
Yes. Since board data is readable through monday's GraphQL API, it's genuinely possible to feed it into a separate BI tool or combine it with data from other systems, rather than relying on dashboard widgets as the only view.
There's a Workforms and account-level analytics area on higher tiers covering usage and activity patterns, but it's aimed at how your team is using monday.com itself, not at business metrics that live in other systems.