> 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.md).

# Player Intelligence

Manage individual player limits and restrictions

Manage individual players with custom limits, restrictions, and behavioral analysis. Player Intelligence gives you granular control over each bettor on your platform.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-946dca6b415fb8235bb847f4179d660079da6acd%2Fimage.png?alt=media" alt="Player Intelligence player profile"><figcaption></figcaption></figure>

***

## Overview

Player Intelligence provides:

* **Player List** — View all players with search and filtering
* **Player Dashboard** — Review each player's metrics and full bet history
* **Individual Limits** — Override your platform limits for a specific player
* **Player Blocking** — Instantly restrict betting access
* **Player Segmentation** — Assign each player a segment, automatically or manually

***

## Available Controls

### Platform Limits (per player)

Apply custom limits for one player. Filled fields override your platform limits, and empty fields inherit them:

| Limit                 | Description                                           |
| --------------------- | ----------------------------------------------------- |
| **Platform Max Risk** | Maximum risk tolerance for this player                |
| **PreMatch rules**    | Stake, odds, and winnings limits for PreMatch markets |
| **InPlay rules**      | Risk and winnings limits for InPlay markets           |
| **Outrights rules**   | Single-bet limits for outright markets                |

[Configure Player Platform Limits →](/u/defend/step-4-player-management/player-platform-limits.md)

***

## Player Actions

| Action           | Description                              |
| ---------------- | ---------------------------------------- |
| **Block Player** | Immediately prevent all betting activity |
| **Set Limits**   | Configure custom betting restrictions    |
| **View History** | Review past betting activity             |
| **Segmentation** | View or change the player's segment      |

***

## Related

* [Player List](/u/defend/step-4-player-management/player-list.md) — Navigate the player directory
* [Player Intelligence Dashboard](/u/defend/step-4-player-management/player-intelligence-dashboard.md) — Review player metrics and bet history
* [Risk Controls](/u/defend/risk-controls.md) — Platform-wide limit configuration
* [Bet Monitor](/u/defend/bet-monitor.md) — Track player betting in real-time


---

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