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

# Progress Portal

The Progress Portal answers the most common question during a rollout — *"how far along is this device?"* — for people who don't need (and shouldn't have) access to session details: helpdesk staff, on-site technicians, or the end users themselves. It is the only page members **without a role** can access.

## How it works

1. Enter the device **serial number** (or device name) and click **Check Status**.
2. The page shows a friendly, color-coded status — *Setting up your device…*, *Setup complete!*, or *Setup encountered an issue* — with the device name and model, an **overall progress bar with percentage**, and the seven enrollment phases as a step list (completed / current / failed).
3. During the app-installation phases, a live activity panel shows what is currently **downloading** (per-app progress, download rate, bytes) and **installing** (elapsed timer), plus a running *X of Y apps installed* counter.
4. On success the total setup time is shown; on failure a short reason or a *contact your IT department* fallback.

Everything updates live — no refreshing needed. The view is strictly read-only: no filters, no drill-downs, no admin controls, and no access to timelines or device internals.

{% hint style="info" %}
**Rollout tip:** during large deployments, give the field technicians the portal URL and the device serials — they can watch each device's progress without anyone granting portal roles or answering status calls.
{% 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.autopilotmonitor.com/portal-guide/progress-portal.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.