> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/defend/step-4-player-management/player-list.md).

# Player List

**Navigating to the Screen**

* From the left side menu, click on **"Player Intelligence"**.

#### **layer List Table Overview** <a href="#player-list-table-overview" id="player-list-table-overview"></a>

On the left side of the screen, you will see a **Player List Table** displaying all registered players.\
The table includes the following columns:

* **Player ID** (Sorted by default in ascending order)
* **Player Name**
* **Player Status**
  * Status is displayed as: **Active** or **Blocked**
  * By default, all players are marked with the status: **Active**

#### **Blocking a Player** <a href="#blocking-a-player" id="blocking-a-player"></a>

**Steps:**

1. Identify the player you wish to block.
2. Click the **"Block"** button next to their name (visible if the player is currently Active).

**Confirmation Dialog:**

* A popup will appear with the message:

  *"Are you sure you want to block this player? This will stop them from betting and affect their account activity."*
* **Buttons:**
  * **Confirm**: Proceeds with blocking the player.
    * The player’s status is updated to **Blocked** in the table.
  * **Cancel**: Closes the popup with no changes made.

#### **Activating a Player** <a href="#activating-a-player" id="activating-a-player"></a>

**Steps:**

1. Identify the player marked as **Blocked**.
2. Click the **"Activate"** button next to their name.

**Confirmation Dialog:**

* A popup will appear with the message:

  *"Are you sure you want to activate this player?"*
* **Buttons:**
  * **Confirm**: Proceeds with activating the player.
    * The player’s status updates to **Active** in the table.
  * **Cancel**: Closes the popup with no changes made.

#### **Important Notes** <a href="#important-notes" id="important-notes"></a>

* Status changes only take effect after confirmation.
* All changes are immediately reflected in the table according to the system's design.
* **Blocking a player will prevent them from placing bets until reactivated.**

#### Manual Player Segmentation

Player segmentation lets you **assign custom labels to individual players** directly from the Player List so teams can quickly identify risk profiles, behaviour patterns or business priorities.

Segments are persistent, visible across DEFEND screens, and help provide consistent context for trading or risk decisions.

Use segmentation to mark players as **VIP, New, Sharp** and **Monitored** relevant to your workflow.

To segment a player, open the player's row in the Player List, click the segment label field, and select or create a segment from the dropdown.

Once applied, the label appears on the Player List and in other relevant views (such as Bet Monitoring and Bet Referral), giving instant visual context about the player's profile.


---

# 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.lsports.eu/u/defend/step-4-player-management/player-list.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.
