# Read the Overview dashboard

> What each role sees on the console’s first page and how to read its numbers.

Source: https://diakrin.com/docs/dashboard

**Overview** is the first page in the console's navigation and opens by default. Bookmarked app, setup and account pages still open directly.

## What each role sees

| Role | What Overview shows |
| --- | --- |
| Builders | The apps you can access, their delivery stages, preparation or review steps, deployment outcomes and a selected app's usage report |
| Owners and IT administrators | Review decisions you are allowed to make, operational attention, infrastructure setup assignments and verified live targets when evidence is available |
| Technical administrator | Operational and setup information, without approval or financial authority |

## Move from a number to the records

Use the links on each card, such as **See apps**, or the linked stage counts to open the records behind a number. A stage link opens a matching authorized app when it appears in the recent work list; otherwise it opens the filtered list.

The activity period offers 7, 30 or 90 UTC days. Daily graph values are also available in the data table under each chart.

## Read the numbers carefully

- **Different things are counted separately.** Projects, native app identities and app/environment candidates are different counts.
- **The delivery snapshot is a distribution, not a funnel.** It shows where apps are now, not how many converted from one stage to the next.
- **A recorded success is not proof of live.** Deployment activity counts each attempt once. Current serving evidence stays separate from a newer release's progress or failure.
- **Unknown is not zero.** An unknown live count means current verification is unavailable or incomplete, not that no apps are deployed. Expired live evidence is removed and refreshed.
- **Assignments are not usage.** Setup assignments do not show live use or capacity. Usage reports show their period, freshness and coverage, and people are not added up across apps.

## App requests on the Adoption page

**Govern → Adoption** shows **App requests** for apps served through the anonymous app gateway. Choose 7, 30 or 90 UTC days.

- **Served** counts requests the app answered with a 2xx status. Redirects are not followed, so a 3xx answer is not served. **Refused or non-2xx** counts requests the gateway refused after checking policy, or that the app answered with a non-2xx status. A non-2xx answer from the app still reaches the visitor.
- A request is counted when the gateway authority admits its outcome. A request can be counted even if the visitor's connection drops afterwards, so a count does not prove delivery.
- **Last request** is the newest counted request. Counts are written when the request is admitted, so there is no delay.
- Each row is one app, environment and release. The release is the deployed artifact digest. A new release starts a new row; counts never reset on a gateway restart or a routine health refresh.
- Not counted: gateway health checks, the gateway's own internal checks and requests refused before a policy was read. Each browser retry is a separate request. There is no sampling.
- Request counting is part of admission: if a request cannot be counted, it is refused.
- Counts are kept for 400 days; the report covers up to 90 days.
- Anonymous visitors are not counted as people. Their requests carry no identity, so there is no unique-visitor number.
- Request estimates for apps that do not use the gateway are a different source and are not added to these totals. This card is separate from **Apps used** on the same page, which uses cloud request estimates and company sign-ins.
- If a window holds more than 500 app releases, the report is refused; choose a shorter window.
