> For the complete documentation index, see [llms.txt](https://docs.resifactory.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resifactory.net/the-console/dashboard.md).

# Dashboard

The landing page. Two things: how your mailboxes are doing, and what has just arrived.

<figure><img src="/files/9TlpzzVkYidqQ62SLAFB" alt="The dashboard with the status strip and recent mail list"><figcaption></figcaption></figure>

## The status strip

| Figure            | What it counts                                                                         |
| ----------------- | -------------------------------------------------------------------------------------- |
| **Accounts**      | Every mailbox you own. Click to open [Accounts](/the-console/accounts.md).             |
| **Healthy share** | The percentage that are `healthy`. In normal operation this sits in the high nineties. |
| **Healthy** 🟢    | Working and fetching mail.                                                             |
| **Degraded** 🟠   | Reachable but unreliable right now. Often temporary.                                   |
| **Expired** 🔴    | Not currently able to fetch mail.                                                      |
| **Pending** 🔵    | Newly added, not yet confirmed working.                                                |

Every status figure is a link — clicking one opens [Accounts](/the-console/accounts.md) filtered to that status, which is the fastest way to see exactly which mailboxes are affected.

The bar underneath shows the same proportions visually. Hovering a segment gives you the exact count and percentage.

{% hint style="info" %}
A handful of non-healthy mailboxes is normal at any given moment — providers throttle, sessions expire, things recover. Worth investigating when the share moves sharply or stays down. See [Accounts](/the-console/accounts.md).
{% endhint %}

## Recent mail

The ten most recent messages across every mailbox you own.

Each row shows when it arrived, who sent it, and the subject. **Bold means unread.** Clicking a row opens it in the [Inbox](/the-console/inbox.md).

### Right-click a row

| Action                          | What it does                                                                                    |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Open**                        | Opens the message in the Inbox.                                                                 |
| **Filter inbox to this sender** | Jumps to the Inbox filtered to that sender — useful for "show me every code from this service". |
| **Copy subject**                | Copies the subject line.                                                                        |
| **Copy from**                   | Copies the sender address.                                                                      |

**Open inbox** in the section header takes you to the full [Inbox](/the-console/inbox.md).

## If recent mail is empty

The dashboard says so explicitly rather than showing a blank list. Usual reasons:

* The mailboxes are new and have not received anything yet.
* Nothing has arrived within the server's retention period — see [Limits and retention](/reference/limits.md).
* The mailboxes are not fetching. Check the status strip: a large **Expired** or **Degraded** count is the tell.

{% hint style="info" %}
The dashboard is **not** filtered by any [inbox window](/imap/inbox-window.md). Windows are an IMAP-only setting; the console always shows everything retained. So if a message appears here but not in your IMAP client, the window is the reason — and that is working as configured.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.resifactory.net/the-console/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
