> ## Documentation Index
> Fetch the complete documentation index at: https://tbignite.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Status definitions

> Every status a user or account can hold in Tickblaze Manager, and what it means for operations.

Every status a user or account can hold, and what it means when you operate. Use this alongside the [Glossary](https://tbignite.mintlify.site/glossary.md).

## User status

| Status | Meaning |
| - | - |
| Enabled | The user record is active. |
| Disabled | The user record is deactivated; the person cannot operate. |

## Account status

| Status | Meaning |
| - | - |
| Active | The account is trading normally, within its rules. |
| Passed | The account met its phase target and advanced or completed. |
| Phase verification reqd ('reqd' is short for 'required' - the account has met its target and is waiting on verification before it advances.) | The account has met its target and is awaiting a **manual review by your firm** before it advances to the next step. **The trader cannot trade this account while it sits here** - your support or risk team has to clear it. It is per account: the trader's other accounts are unaffected. The control for clearing it is not currently exposed in the interface, so ask the Tickblaze team if you have accounts waiting. |
| Failed | The account breached its **max drawdown**, hit its daily limit with **Check daily drawdown** on and **Soft breach** off, ran out of [Total trading days](https://tbignite.mintlify.site/challenge-phases.md#targets) before completing the phase, or was failed manually. It can no longer trade. **The engine never reverses a failure** - no later recovery, session, or close un-fails it. An authorized operator can still set the account back to Active (Update status on [Account details](https://tbignite.mintlify.site/account-details.md), or the [Bulk account editor](https://tbignite.mintlify.site/bulk-account-editor.md)); that is a deliberate firm-side correction and is recorded in Account events. A **soft** daily breach is different - it stops the account for the session only. See [How drawdown & failure work](https://tbignite.mintlify.site/drawdown-and-failure.md). |
| Blocked | No actions or changes can be made on it, and it cannot trade. The underlying state may still be Active or Failed. **To clear it**, right-click the account row on [Accounts](https://tbignite.mintlify.site/accounts.md) and choose **Enable / unblock account**. |

**The account lifecycle at a glance:**

```mermaid theme={null}
stateDiagram-v2
    state "Phase verification reqd" as PhaseVerif
    [*] --> Active: created through the API
    Active --> PhaseVerif: profit target and minimum trading days met
    PhaseVerif --> Passed: verification passes
    Passed --> [*]: next step issued as a new account
    Active --> Active: final phase, nothing left to pass, keeps trading
    Active --> Failed: max drawdown / hard daily breach / out of Total trading days / manual fail
    Failed --> Active: operator reactivation, recorded in Account events
    Active --> Blocked: put under review
    Failed --> Blocked: put under review
    Blocked --> Active: block cleared, underlying state was Active
    Blocked --> Failed: block cleared, underlying state was Failed
```

> [!NOTE]
>
> An account can be failed **automatically** (a **max drawdown** breach, or a daily breach with **Soft breach** off) or **manually** (through Update Status on the account). Either way, the change is recorded in Account Events.

## Trading capability

**Trading status** is the roll-up of the signals below - a user can place a trade only when every one of these allows it. If any one of them prevents it, no trade can be placed.

| Signal | Prevents trading when |
| - | - |
| User status | It is set to Disabled. |
| Blocked | The user is Blocked. |
| Account state | The account is Failed or Blocked. |
| Entitlement | A required market-data entitlement (Permission for one user to receive a particular exchange's market data.) is missing. |

> [!NOTE]
>
> **KYC is not on that list, and that is deliberate.** An outstanding or rejected KYC verification does **not** stop a trader trading today - the platform has no check that gates trading on KYC. The **KYC verification required** badge is informational. **This is changing.** Once the KYC vendor integration is finished, a phase will be able to *require* KYC, and a trader will only be able to trade that account once their verification is approved. Until then, enforcing it is your own process.

## KYC verification

| State | Meaning |
| - | - |
| Pending | A verification request has been sent but not yet completed. |
| Approved | Identity confirmed by the provider (shown as **Approved** on the KYC (Know Your Customer - the identity checks a trader completes with your firm's verification provider.) tab). |
| Rejected | The provider could not verify the identity. |
| Expired | A previously valid verification has passed its valid-until date. |

## Account Details badges

The Account Details header shows quick-status badges. The most common:

| Badge | Meaning |
| - | - |
| Sim / Live | The account's **mode**, not its status: **Sim** is simulated and **Live** is real money. Tickblaze offers Sim only today, so accounts show **Sim**. |
| KYC verification required | The trader still needs to complete identity verification with your firm's KYC provider. |

> [!NOTE]
>
> Which badges and states appear depends on your tier and configuration - some show only when a feature such as KYC is enabled for your firm.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.