> For the complete documentation index, see [llms.txt](https://docs.b2prop.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2prop.b2broker.com/admin-guide/view-a-list-of-prop-challenge-accounts.md).
# View a list of prop challenge accounts
When clients start a challenge, the trading accounts with the specified initial balance are opened for them on the respective platform.
You can monitor prop challenge accounts engaged in a specific challenge and track their progress as follows:
{% stepper %}
{% step %}
Go to **Prop trading** > **Challenges list**.
{% endstep %}
{% step %}
Select the challenge and click **Edit**.
{% endstep %}
{% step %}
For real challenges, go to the **Live Accounts** tab.\
For trial challenges, go to the **Demo Accounts** tab.
{% endstep %}
{% endstepper %}
Live Accounts tab
On both tabs, you can view a list of accounts that have started the challenge along with the following information about their progress:
**Processing status**\
\&#xNAN;*Applicable only for live accounts*
The status, which is manually changed, to indicate if a funded account has been created for the prop challenge account that successfully passed a challenge:
* **Not processed** – no funded account has been created yet
* **Processed** – a funded account was created
For details, refer to [Mark trading accounts passed a challenge as processed](/admin-guide/create-a-funded-account/mark-trading-accounts-passed-a-challenge-as-processed.md).
***
**Status**\
The status assigned to the process of passing a challenge. Possible values:
* ACTIVATION – a trading account for a challenge is being created for a client.
* STARTED – a challenge is in progress by a client. The challenge requirements haven't yet been met.
* SUCCESS – a challenge step was successfully passed. If a challenge includes only one step, the status indicates that the challenge was successfully completed.
* FAIL – a challenge was failed because the challenge requirements weren’t met.
***
**Plan**\
The identifier of a challenge plan.
***
**Step**\
The number of a challenge step.
***
**Login**\
The account number (login) used for passing a challenge.
***
**Currency**\
The currency in which the account is denominated.
***
**Starting balance**\
****The initial balance on the account.
***
**Balance**\
The current balance on the account.
***
**Equity**\
The current equity on the account.
***
**User ID**\
The identifier of a client participating in a challenge.
***
**Name**\
The client’s name.
***
**Email**\
The client’s email address.
***
**Created**\
The date and time when a client started a challenge and the MT or cTrader account was created.
---
# 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.b2prop.b2broker.com/admin-guide/view-a-list-of-prop-challenge-accounts.md?ask=&goal=
```
`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.