> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/agency-white-label/apps/find-customers-apps.md).

# Find customer's apps

### Where can I find all my customer's apps?

The Apps screen in your Agency dashboard provides a centralized view of all the apps created under your Agency account. This overview allows you to quickly monitor key details about each app, manage settings, and take action when needed.

{% embed url="<https://scribehow.com/shared/Find_customers_apps__Z9eibONbR_K6HPwBnWFWBQ>" %}

#### App

* Shows the App Name and App ID.
* Helps you quickly identify and reference each app.
* Clicking the app name will take you to the app’s dashboard where you can access your customer's app.&#x20;

#### Domain

* Displays the web domain associated with the app.

#### Type

* Indicates the App Type, such as WordPress or Custom App.
* Helps you differentiate between different kinds of builds.

#### Downloads

* Shows the number of app downloads separately for:
  * Android (with Android icon)
  * iOS (with iOS icon)
* This helps you track user adoption across platforms at a glance.

#### Plan

* Displays the current subscription plan associated with the app.
* This helps you identify apps on Free, Basic, Pro, Premium, or any other plan tier.

#### Created

* Indicates the creation date of the app.
* Useful for sorting or tracking the age of different client apps.

{% hint style="success" %}
The Apps screen allows agencies to efficiently monitor the status and lifecycle of every client app, all from a single view.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/agency-white-label/apps/find-customers-apps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.