01
Collected in the background
An hourly pass mirrors Monday’s activity log into a database of our own. First enrolment backfills several months of history so even the first open has something to compare against.
Monday.com add-on
Executive dashboard for Monday.com
Team activity per colleague, per board and per field — inside Monday, without spending the workspace’s API budget.
- Where it runs
- inside the Monday.com UI
- Data source
- Monday’s activity log
- API cost per open
- zero calls
An executive dashboard inside Monday.com: it shows what colleagues did on the boards over the last closed periods — per colleague, per board, per activity type and per field — and what is coming due. It works from Monday’s own activity log, and opening it consumes nothing from the workspace’s API budget.
The question it answers
Monday shows activity item by item. When a company head asks what one colleague did this month across five boards, the only way to answer inside Monday is to open the items one at a time. That view did not exist — an overview of what colleagues did on the boards was an explicit customer requirement.
Who it is for
Built for an owner, CEO or head of sales at a company size where one person still wants a per-colleague read but can no longer get it by scrolling boards.
What it shows
Every panel works on closed periods, and each measures itself against the preceding window of equal length.
Headline numbers
Total actions, active colleagues and the automation share in one row. Automation is kept separate: events from system actors never inflate any colleague’s count.
Activity per period
Weekly or monthly bars with a cumulative overlay, beside an actions-per-active-day measure — the latter normalises for people who work in bursts rather than evenly.
Per colleague
Two doughnut rings side by side: this period and the previous one. Ring thickness carries the period total and a colour stays with the same person across both rings, so weight and composition read at once.
Comparison table
Actions per colleague against the preceding window of equal length, marked up, down or flat. Movement inside a ±10% band counts as flat, so noise does not read as a trend.
By board and by type
Activity by board and by event type. Boards are named by the system’s own role vocabulary — Accounts, Opportunities, Tasks, qualified and unqualified contacts — not by whatever the customer typed.
Where the work went
Seven board-scoped stacked panels: activity by category over time with a three-period moving average; which fields absorbed the work; who worked when; the most-touched records by field; and the three pairings of category, type and colleague.
Status changes
From → to status movements in order of frequency, as text rather than as ids. The viewer picks the status field from those that actually saw movement in the window.
Upcoming tasks
Tasks due per day, beside the overdue, due-today and next-seven-days counts. This is the only panel that looks forward rather than back.
Where the data comes from
The surface does not ask Monday on every open. A background pass mirrors the activity log ahead of time, and the dashboard computes from that mirror.
Monday.com
activity log, per board
hourly
Our own database
hourly mirror, months of history on first run
0 API calls
Dashboard
computed from the mirror
02
Opening it calls no Monday API
The dashboard computes every figure from that mirror. Opening and refreshing it costs zero Monday API calls — however often it is opened, the workspace budget is untouched.
03
Closed periods only
The in-progress week or month is excluded from every figure, and each one is compared against the preceding window of equal length. A half-finished week cannot look like a decline.
04
A key per workspace
There is no shared API key: every workspace works with its own OAuth token, and a test fails the build if any code path reaches for a shared one. One customer’s traffic cannot spend another’s quota.
Who can see it
This surface shows per-colleague performance data, so being able to use the app is not enough on its own. The dashboard has its own allowlist, independent of app access.
Closed by default
An empty list denies everyone. The question is not who was excluded but who was let in — and while that is nobody, nobody sees it.
Self-locking
While the list is empty anyone may set it. After that only someone already on it can change it, and a save that would leave nobody able to edit it is rejected.
The tab does not appear
A colleague not on the list never sees the tab — not greyed out, simply absent. The server re-checks at every endpoint; hiding it is presentation, not the protection.
No raw ids anywhere
When an actor’s name cannot be resolved it renders a generic label, never the internal Monday id. In long lists the remainder folds into a single neutral everyone-else slice, which the chart never colours as though it were a person.
Where it stands
The dashboard is in production use at a sales organisation working its pipeline in Monday.com. We have not run an impact study — no time-saved figure, no pre-rollout baseline — so we state no such number here. What you read above describes how it works; it is not a promise.
If your company runs its pipeline in Monday.com and the executive read is missing, let us look at what this surfaces on your own boards. The first round is a conversation, not a rollout.
Let us look at your own boards
Tell us what you run in Monday.com and we will work out which parts of this executive view would be useful to you. The first round is a conversation.