> This page is for Workforce.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Dashboard

> What each Dashboard tab reports: adoption and spend on Overview, model routing and cost on Routing, and Connector and tool reliability on Tool calls.

The [Dashboard](https://wf-develop.merge.dev/dashboard) is where you check a number. It reports what your organization spent, who is using AI, which models answered, and which tools succeeded, and it stops there. When you want a conclusion with a fix attached instead, read [Insights](/merge-workforce/insights).

Three tabs, and a window picker offering the last 7 or 30 days. Trends compare the first half of the window against the second, so a 7-day view reacts fast and a 30-day view is the one to quote.

## Overview

Adoption and spend together, which is the pair worth reading first.

| Card                           | What it tells you                                                                                                        |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| **Daily active employees**     | Employees making requests each day, with a trend. Headcount with access is not adoption, so this is the number to report |
| **Budget this month**          | Month-to-date spend against your Group budgets. See [Budget](/merge-workforce/models/budget) to set them                 |
| **Top tools**                  | The tools carrying the most calls, which is where a skill or a Tool Pack change pays off most                            |
| **Top models by spend**        | Where the model bill actually goes, rather than where you assume it goes                                                 |
| **Average spend per employee** | The figure to compare across teams, since a Group of 4 and a Group of 200 are not comparable on totals                   |

## Routing

How your [routing policies](/merge-workforce/models/routing) are behaving, and what the models cost.

Cost per LLM call and credits used per month carry the trend. Spend by model, by vendor, and by provider answer the same question at three levels of detail, so start at model and widen only when a number surprises you. Tokens per day splits input, output, and cache reads, which is how you tell a workload that grew from one that stopped using the cache.

**Gateway coverage by harness** is the rollout number, not a cost number. It says which AI clients are actually routing through Gateway, and a harness missing from it is a harness producing no telemetry at all. Absence of traffic looks the same as absence of work, so read it against your employee list rather than on its own. [Roll out models](/merge-workforce/rollout/models) covers closing those gaps.

## Tool calls

Whether the tools you granted are working.

Success rate by Connector and by tool are the two reliability views: the Connector view finds a broken integration, the tool view finds one bad action inside a working Connector. Tool calls and credits by group show adoption per team, and credits and calls per tool show which tools are worth their cost.

A failure rate here is a real problem to chase, and [Tool call logs](/merge-workforce/logs/tool-calls) is where you chase it, one call at a time.

> **Note**
>
> Cards fall back to their own empty state rather than blanking the tab, so a Dashboard with model data but no tool calls renders the half it has.

## Next

For findings that name what to change rather than numbers to interpret, read [Insights](/merge-workforce/insights).