> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Digital Labor Dashboard

> Measure the work Elementum AI agents and automations perform, expressed as full-time-employee (FTE) equivalents, with trends, breakdowns, configurable time rules, and export

The Digital Labor dashboard quantifies the work your Elementum AI agents and automations perform and expresses it as a full-time-employee (FTE) equivalent. It gives Organization Administrators a single place to measure and communicate the productivity value the organization gets from Elementum.

Find it in **Organization Settings** under the **Analytics** section, on the **Digital Labor** page.

<Info>
  Digital Labor figures are approximations meant to communicate productivity value. They are based on an estimated time each action would take a person to complete manually — a default estimate out of the box, which you can refine with your own time rules.
</Info>

## How the FTE calculation works

Elementum builds the FTE figure from the actions your digital workforce completes:

* **Successful actions only.** Failed and skipped agent runs and automation executions are not counted.
* **A time estimate per action.** Each action is assigned an estimated manual handling time — 5 minutes by default — representing how long the task would take a person to do by hand.
* **Total hours.** The number of successful actions is multiplied by the time per action to produce the total productive hours.
* **FTE equivalent.** The total hours are divided by a full-time workload for the period — 8 hours per working day. For a 90-day period, that denominator is `90 days × 8 hrs = 720 hrs`.

The headline at the top of the dashboard states the result in plain language — for example, "Your digital workforce delivered the output of 2.30 full-time employees" — and splits the figure into **Agents** and **Automations** contributions.

Each headline metric has an inline hover tip that explains how the figure is calculated.

## Choose a time period

Use the period selector in the top-right corner to set the window the dashboard reports on. Preset options are **Last 7 Days**, **Last 30 Days**, and **Last 90 Days**. The dashboard opens to the last 30 days by default.

The selected period drives every metric, the trend chart, the breakdowns, and the export.

<Note>
  The dashboard is environment-aware: it reflects the environment you currently have selected. Switching environments changes the data shown.
</Note>

## Digital Labor breakdown

Below the headline, the breakdown section shows the numbers behind the FTE figure for the selected period:

| Metric                    | What it shows                                                                                                                                 |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agent Actions**         | The count of successful agent executions.                                                                                                     |
| **Automation Actions**    | The count of successful automation executions.                                                                                                |
| **Total Hour Equivalent** | The total productive hours delivered by your digital workforce, split into the share contributed by agent actions and by automation actions.  |
| **FTE Calculation**       | The total hours, the period hours used as the denominator (for example `90 days × 8 hrs = 720 hrs`), and the resulting Digital Workforce FTE. |

## FTE trend

A stacked bar chart plots FTE over time for the selected period, with one bar per day. Each bar is split into the share contributed by agents and the share contributed by automations, so you can see how digital labor accumulates day to day and where it comes from. The trend also surfaces the highest and lowest days and the number of active apps contributing over the period.

## Break down by app, agent, or category

Tabs at the top of the table let you view your Digital Labor by:

* **By App** — Contribution grouped by the app each action ran in.
* **By Agent** — Contribution grouped by the agent or automation that performed the action.
* **By Category** — Contribution grouped by the categories you define (see [Categories](#categories)).

Apps and agents are defined by the platform. Categories are labels you create yourself. Actions that have not been assigned a category are grouped under **Uncategorized** so nothing is left out.

## Improve accuracy with time rules

Out of the box, every action uses the default 5-minute estimate. The most effective way to make the dashboard reflect your organization is to set your own time estimates. A coverage indicator on the dashboard shows the percentage of actions covered by a custom rule versus the default, and links to the settings where you refine them.

Open the settings from the **Settings** button in the top-right corner of the dashboard (or the **Customize** prompt in the coverage banner), then use the **Rules** tab.

### Add a time rule

A rule sets the human-equivalent time for the actions it targets, and can narrow the scope to just the actions or agents you care about.

1. On the **Rules** tab of Digital Labor settings, click **Add Rule**.
2. Under **Where does this rule apply?**, choose the scope:
   * **App** — A specific app, or **Any app**.
   * **Action type** — A specific action type, or **Any**.
   * **Specific agent or task** — A specific agent or task, or **Any**.
3. Under **Human-equivalent time per action**, enter a **Value** and choose a **Unit** (for example, 5 Minutes) for how long the task would take a person to complete manually.
4. Optionally, assign one or more **Categories** to the actions the rule covers.
5. Review the summary showing which actions the rule will apply to, then click **Add Rule**.

**Behavior notes:**

* Rules apply **retroactively** — updating a rule recalculates the metrics across all past runs the rule covers, not just future activity.
* Use a broad "umbrella" rule to set a single time for a shared action type across many agents, then add narrower rules for the specific agents, tasks, or apps that need a different estimate.
* Any action not covered by a rule continues to use the 5-minute default.

## Categories

Categories are free-form labels, scoped to your organization, that let you group actions into the buckets that matter to you — for example, Finance or a specific department. They are not configured automatically; you create and assign them yourself.

Manage them on the **Categories** tab of Digital Labor settings, and assign categories to actions when you add or edit a time rule. A single category can be applied to actions across multiple agents, tasks, and apps, and an action can carry more than one category.

Once categories are assigned, use the **By Category** tab on the dashboard to see your Digital Labor broken out by them. Actions with no category appear under **Uncategorized**.

## Export the data

Click **Export** in the top-right corner to export the dashboard data for the selected time period. The export is generated as an Excel (`.xlsx`) file and includes the overall metrics, the daily breakdown, and the by-app, by-agent, and by-category breakdowns. Uncategorized actions are included in their own section so nothing is missed.

The file is prepared in the background. Download it from **Background Tasks** in your profile once it is ready.

## Access and permissions

Organization Administrators have access to the Digital Labor dashboard automatically. You can grant access to other users as well.

The aggregate figures at the top of the dashboard — the headline FTE, the Agent and Automation Actions, and the Total Hour Equivalent — always reflect the full organization, whether or not the user has access to every object behind them. Access scoping applies only to the breakdown table: in the **By App**, **By Agent**, and **By Category** views, a non-admin user sees only the apps, agents, and categories they have access to.
