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

# Dashboard

The dashboard is the main interface of the WiFi Pineapple Pager.

### Power menu  <a href="#power-menu" id="power-menu"></a>

<figure><img src="/files/cTqMuidz6Z022yxz1zoD" alt=""><figcaption></figcaption></figure>

Access the power menu by double-tapping the power button - the recessed button on the top left of the pager.

The power menu allows you do perform a clean shutdown, lock the device, and enable some extra statistics on the UX engine.

Press and hold the power button for 5 seconds to force a power-off; **only do this if the normal shutdown menu is not available** as it has the potential to corrupt data!

{% hint style="info" %}
It’s always a good idea to cleanly shut down your device!\
\
Forcing a power-off may corrupt some data if it is actively being written.
{% endhint %}

### Alerts  <a href="#alerts" id="alerts"></a>

<figure><img src="/files/hx2DStVWo0xAQEeqffPT" alt=""><figcaption></figcaption></figure>

Alert payloads are raised by events generated by nearby devices. Clients connecting to the WiFi Pineapple access points on the Pager, capturing WPA handshake data, detecting Wi-Fi denial of service attempts, and more can all generate alerts.

### Payloads  <a href="#payloads" id="payloads"></a>

<figure><img src="/files/cG0R9Eaex1MWIEluOvXF" alt=""><figcaption></figcaption></figure>

User payloads form the heart of the expandability of the WiFi Pineapple Pager. Written in standard `bash` script (an extremely powerful, but easy to use, scripting system and shell which is used in millions of Linux and Unix based systems) and enhanced with Hak5 Duckyscript commands (simple shortcuts to perform powerful actions and interact with the WiFi Pineapple Pager UI and more), payloads are where you can launch custom commands, script repeatable behavior, and more.

### Recon  <a href="#recon" id="recon"></a>

<figure><img src="/files/RLvltmIhr12cT769Ysk3" alt=""><figcaption></figcaption></figure>

Recon is where the WiFi Pineapple Pager flexes the radio capabilities. Monitor the airspace around you, with displays for Wi-Fi traffic, packet rates, and discovery of new access points and devices.

Then, interactively drill down into the wireless environment and get detailed information about encryption configurations, client counts, and advanced WiFi behavior of discovered devices - and leverage the power of the payload system to run custom actions against clients and access points!

### PineAP  <a href="#pineap" id="pineap"></a>

<figure><img src="/files/izPIh8mtaEXUoEIofNEf" alt=""><figcaption></figcaption></figure>

The PineAP suite hosts the WiFi Pineapple active device impersonation - configure Open AP impersonation, mimicked SSID lists, Evil WPA, and more.

### Settings  <a href="#settings" id="settings"></a>

<figure><img src="/files/aj2NWf8q5VJvlRw2PgnB" alt=""><figcaption></figcaption></figure>


---

# 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://documentation.hak5.org/wifi-pineapple-pager/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.