# Entity Limits

Fine-tune your risk settings with granular control at the sport, competition, or fixture level. Entity Limits use a hierarchical tree layout for precise, scalable risk management.

***

## Access

Navigate to **DEFEND** → **Risk Controls** → **Entity Limits** (Sports Limits tab) in the platform sidebar.

***

## Prerequisites

Entity limit configuration depends on your feed integration. **You must stream feed data to apply entity limits upon the entities structure/hierarchy.**

***

## Page Layout

The page is divided into two sections:

| Section                  | Description                                    |
| ------------------------ | ---------------------------------------------- |
| **Limits Table**         | Displays existing sports limits                |
| **Limits Configuration** | Configuration panel for selected or new limits |

***

## Limits Table

### Table Columns

| Column           | Description                                   |
| ---------------- | --------------------------------------------- |
| **Entity Limit** | Hierarchy level (Sport, Competition, Fixture) |
| **Type**         | PreMatch / InPlay                             |
| **Sport**        | Sport name with icon                          |
| **Location**     | Location name with icon                       |
| **Competition**  | Competition name                              |
| **Fixture**      | Fixture name                                  |
| **Start Date**   | Fixture start date                            |
| **Max Winning**  | Maximum winnings allowed                      |
| **Action**       | Reject                                        |

### Table Features

* **Sorting:** By sport name (A-Z)
* **Search:** By amount, action, type, entity limit, sport name, location, competition, or fixture
* **Filters:**
  * Entity Limit (hierarchy level)
  * Sport (dropdown of all sports)
  * Action (Check or Reject)

***

## Limits Configuration

### Configuration Fields

| Field           | Description                | Default  |
| --------------- | -------------------------- | -------- |
| **Type**        | PreMatch, InPlay, or Mixed | PreMatch |
| **Sport**       | Select from dropdown       | —        |
| **Location**    | Select from dropdown       | —        |
| **Competition** | Select from dropdown       | —        |
| **Fixture**     | Select from dropdown       | —        |
| **Max Winning** | Maximum winnings allowed   | —        |
| **Action**      | Reject or Check            | Reject   |

**Validation:**

* Numeric values only (min: 1, max: 100,000,000)
* Value cannot exceed the maximum winning of the parent hierarchy level
* Lower hierarchy can only have equal or lower amounts

***

## Creating a New Limit

1. Click **+New**
2. Fill in the fields in order: **Type → Sport → Location → Competition → Fixture**
3. Enter **Max Winning** amount
4. Select **Action** (Reject or Check)
5. Click **Save Limit**

***

## Editing a Limit

1. Select a limit from the table
2. Update Max Winning or Action
3. Click **Save Limit**

***

## Deleting a Limit

1. Select a limit from the table
2. Click **Delete Limit**

The affected entities will revert to platform default limits.

***

## General Restrictions

* Fields must be configured in top-down order: **Type → Sport → Location → Competition → Fixture**
* Can apply limits for any sport type for InPlay, PreMatch, or Mixed
* **Cannot set multiple limits for the same sport and same type**
* **Maximum winning hierarchy:** The maximum winning amount at a lower hierarchy cannot exceed its parent level. For example, if a fixture is set to $500 and the league is later set to $250, the league limit ($250) will apply.


---

# Agent Instructions: 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:

```
GET https://docs.lsports.eu/u/defend/risk-controls/entity-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.