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

# Wall Dashboard

## What Is This Page?

The **Wall Dashboard** is a NOC-style display built to be shown on an office TV or a wall-mounted screen rather than viewed in a normal browser tab. It has a dark, high-contrast theme, large tabular numbers, a live clock, and a fullscreen toggle — and deliberately has almost no interactive controls, so nothing accidentally changes if someone taps the screen.

## Why Would You Use This?

* Keep a permanent status board running in an operations room or team area
* Give the whole team passive visibility into drift status and worker health without anyone needing to open IntuneAssistant
* Spot a spike in drifts or a failed worker at a glance during an incident

## Auto-Refresh

The dashboard refreshes itself automatically every **60 seconds**. A countdown ring in the header shows how long until the next refresh, and a **last updated** timestamp appears in the footer.

## Fullscreen Mode

Click the fullscreen icon in the top-right corner to expand the dashboard to fill the entire screen (using your browser's native fullscreen mode) — useful when displaying it on a dedicated monitor. Click again to exit fullscreen.

## What You Will See

### Top Bar

The IntuneAssistant logo, a live clock and date, a **Worker healthy / degraded / offline** status pill, the refresh countdown ring, and the fullscreen toggle.

### KPI Row

Eight tiles: Active Monitors, Inactive Monitors, Active Drifts, Resolved Drifts, Successful Runs, Failed Runs, Success Rate, and Snapshot Jobs (with a note of how many are currently running).

### Active Drifts

The 10 most recently detected, unresolved drifts — each showing the affected resource, its type, which monitor flagged it, and how long ago it was reported. When nothing is drifting, this panel shows "No active drifts detected — all monitored configurations match their baselines."

### Recent Run History

The last 8 monitor runs, each with a status dot (green success, amber partial, red failed), the monitor name, a small bar indicating the drift count, and the completion time.

### Worker Instances

Up to 6 background worker machines that execute drift checks, each with a health dot (healthy, stale, offline, unknown), its version, and status chips (Enabled, Accepting Jobs, Auto-Update).

### Monitors

Up to 10 monitors with a status dot, name, active-drift count badge, and last run time.

### Recent Snapshot Jobs

The last 5 baseline snapshot jobs with a status dot and timestamp.

{% hint style="info" %}
The Wall Dashboard shows the latest results your monitors have already produced — it does not trigger a live check against Intune itself when it refreshes. Freshness depends on how recently your monitors last ran.
{% endhint %}

## Related Pages

* [Global Overview](/intune-assistant/monitor/global-overview.md) — the interactive equivalent, with drill-down and filtering
* [All Monitors](/intune-assistant/monitor/all-monitors.md)
* [Drifts](/intune-assistant/monitor/drifts.md)


---

# 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.intuneassistant.cloud/intune-assistant/monitor/wall-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.