> For the complete documentation index, see [llms.txt](https://knowledge.whiteintel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.whiteintel.io/your-dashboard/applications.md). # Applications The Applications tab of the Dashboard lists the third-party applications that a domain's exposed accounts also appear on. It helps you understand the wider footprint of a compromise: the external services where the same identities are exposed. **Availability:** All plans for viewing.
### What it shows Applications are split into two classes: * **Consumer** — Regular users (personal email addresses, direct usernames) that has access to the specified application. * **Corporate** — Users with **corporate email prefix** that has access to the specified application. In group views, a source column attributes each application to the member domain it relates to. Each application is itself a registrable domain. On mobile, applications render as cards that present the application, its type, and the source, with a View records action. ### Filtering and search * **Show** — All, Consumer, or Corporate. * **Search** — a substring match on application names. Both are applied server-side, so the totals and pagination reflect the filtered result. ### Viewing records Each application row provides a **View records** action that opens Global Search in a new tab, pre-scoped to the source domain and filtered to the selected application, with the matching record type. This lets you move directly from "where else is this domain exposed" to the underlying records. ### Population time Initial application results may take up to twelve hours to populate for a newly monitored domain. The view states this explicitly when no results are available yet, which is distinct from the case where an active filter simply matches nothing.