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

# Regional Entities

> Understand how a Partner is represented technically in a region and environment.

A **Regional Entity** is the technical representation of a Partner in one region and one environment in DVM.

```text theme={null}
Regional Entity
=
Partner
+
Region
+
Environment
```

For example, one Partner can have separate Regional Entities for EU Production, US Sandbox, and US Production.

## Regional Entity rules

A Regional Entity:

* Belongs to exactly one Partner
* Represents one region
* Represents one environment
* Holds technical configuration needed for that regional environment

Regions and environments are a representation of the technical setup in DVM and do not represent your organizations' entities.

## Partner versus Regional Entity

| Partner | Regional Entity |
| - | - |
| Stable business identity | Technical connection point |
| Region-independent | Represents one region |
| Environment-independent | Represents one environment |
| Used for Partner-level human access | Used for regional technical configuration |

## Human and technical access

Human access is managed at **Partner + Environment** level.

Technical integration can require Regional Entity-level configuration where region and environment matter.

```text theme={null}
Human access
User → Partner → Environment

Technical integration
Partner → Regional Entity → configuration
```

Users do not need to select individual Regional Entities to use Partner-level applications such as Dashboard or Care.

## Routes

A **Route** is the technical connection between two Regional Entities.

For example:

```text theme={null}
Reseller / EU / Sandbox
          │
          │ Route
          │
Content Provider / EU / Sandbox
```

Routes describe technical connectivity. They are separate from the business decision by two Partners to pursue an opportunity together.