> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataerai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Operational dashboard
> Monitor your organization's activity, storage, AI usage, and administrative audit trail from one place — and, for platform operators, the health of the whole platform.
Use the **operational dashboard** to monitor usage and health from one place.
You can review:
* Storage usage.
* Upload and download activity.
* AI-assisted search usage.
* Administrative changes.
* Platform health and DID coverage, if you are a platform operator.
Good to know:
* The dashboard is read-only.
* Make changes elsewhere in [Settings](/account/administration).
* Organization admins see their organization.
* Platform operators can see platform-wide status.
## Who can see it, and what it shows
Two audiences use the dashboard. What you see depends on your role:
| You are | Scope | You additionally see |
| ------------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------- |
| An **organization admin** | **Your organization** — the header reads *Your organization* | — |
| A **platform operator** | **The whole platform** — the header reads *Platform-wide — all organizations* | The **system status** board and the **DID coverage** panel |
The dashboard only shows information you are allowed to see.
## Open the dashboard
Open the **user account menu** in the top-right, then choose **Operational dashboard**. The item appears only if you're an organization admin or a platform operator. Use the logo (top-left) to return home when you're done.
## At a glance
The top row gives a quick count of the things you manage:
* **Organizations**.
* **Users**.
* **Projects**.
* **Collections**.
* **Assets**.
For an organization admin, these counts cover your organization. For a platform
operator, they cover the whole platform.
## Activity
The **activity** section summarizes uploads and downloads over a window you
choose with the **7 / 30 / 90 day** selector. The same selector also controls AI
usage and audit log sections.
| Metric | What it means |
| --------------- | -------------------------------------------------------------------------------------------- |
| **Transfers** | Uploads and downloads started in the window. |
| **Failed** | Transfers that didn't complete — a steady trickle is normal; a spike is worth investigating. |
| **Bytes moved** | Total volume transferred in the window. |
Use it to spot a quiet period, a surge in transfers, or a rising failure rate.
## Storage
The **storage** section shows how much allocated space is in use:
| Metric | What it means |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Used** | Bytes currently stored. Sub-allocations are rolled up into their parent, so the total reflects real usage without double-counting. |
| **Allocations** | The number of allocations (including sub-allocations). |
| **Records** | The number of stored records. |
Rows with a quota also show **utilization**, so you can spot repositories that
are filling up.
## AI usage
The **AI usage** section shows AI-assisted search activity for the selected
window:
| Metric | What it means |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Searches** | AI-assisted searches run in the window. |
| **Tokens** | Total tokens consumed — the basis for any usage budget. |
| **Policy-denied** | Searches blocked by your organization's AI policy. A rising count can mean people are hitting a setting you may want to revisit. |
Use it to see whether usage is comfortable, approaching a limit, or being blocked
by policy.
## Audit log
The **audit log** shows administrative changes.
Use it to answer:
* Who changed something?
* What changed?
* Which item was affected?
* When did it happen?
Organization admins see their organization's entries. Platform-wide events are
visible only to platform operators.
Each entry has four columns:
| Column | What it shows |
| ---------- | ------------------------------------------- |
| **Time** | When the action happened. |
| **Actor** | The person who performed it. |
| **Action** | What was done (for example, a role change). |
| **Target** | The item affected. |
Use **Filter by action** to narrow the list to a single kind of event. The log
uses the same date window as the sections above.
## System status
The system status board is visible to **platform operators** only.
The **system status** board shows whether platform services are healthy.
It covers:
* The console.
* The database.
* Services that move and process data.
* Background workers.
Each row shows a status:
* **up** — the service responded to its health check.
* **active** — a background worker has processed work recently.
* **idle** — a worker is up but currently has nothing to do.
* **down** / **unknown** — a check failed or couldn't be evaluated; start here when something platform-wide looks wrong.
## DID coverage
The DID coverage panel is visible to **platform operators** only.
Every asset, dataset, and person can carry a [DID](/identity/overview) — its
stable, citable identifier. This panel shows how complete that coverage is and
lets you top it up on demand.
| Metric | What it means |
| ---------------- | --------------------------------------------------------------------------------------------------------------- |
| **Coverage** | The percent of objects that already have a DID, with the underlying counts (for example, *13 / 15 have a DID*). |
| **Missing DIDs** | How many objects don't have a DID yet. |
| **Daily check** | When the automatic freshness check is next scheduled to run. |
Below the totals, a per-type breakdown shows coverage for **assets**,
**datasets**, and **people** separately, so you can see where any gap is.
### How DIDs get assigned
* New objects are minted a DID **automatically** when they're created.
* A **daily freshness check** runs in the background and mints a DID for
anything still missing one — for example, records added by a bulk import.
* Select **Run freshness check** to run that sweep immediately instead of
waiting for the daily run; the coverage numbers update as it works. It's safe
to run anytime — objects that already have a DID are skipped.
## Reuse & impact
The **Reuse & impact** panel shows how data is being used across your scope.
Pick a window with the **7d / 30d / 90d** selector at the top right.
* Headline tiles show **Views**, **Downloads**, and **SDK / compute** for the
window, each as a **total** with the **unique** count beneath it (distinct
people or machine clients, not raw repeats).
* A daily chart plots views over the window so you can spot trends and spikes.
* **Top assets by impact** lists the highest-impact assets that saw activity in
the window, with their views and downloads (total / unique).
A platform operator sees activity across all organizations; an organization
admin sees their own organization's assets and the people in it.