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

# Entity schemas

Entity schemas define the structure, validation rules, and identifiable information of data flowing through your integrations. By default, all data is assigned to the default entity type, which has no structure, validation, or identifiable fields. Your Alumio environment comes with a set of standard entity schemas, and you can create your own as needed.

Navigate to **More → System → Entity Schemas** to create and manage entity schemas.

### What Entity schemas can do

* Define the expected structure of data for a specific entity type (e.g. ERP Product, Order).
* Set validation rules on incoming data: required fields, data types, minimum values, and allowed values.
* Define identifier paths that make entities uniquely identifiable across tasks and Storages.
* Automatically filter out data that does not match the defined schema before it reaches the destination system.
* Disable an entity type to pause all integrations that use it.

### Automatic data validation

Entity schemas support JSON schema validation to automatically check incoming data against a predefined structure. A schema can specify:

* Required fields that must be present on every incoming entity.
* Data types per field (e.g. `string`, `integer`, `boolean`).
* Value constraints such as minimum values, maximum values, or a fixed list of allowed values.

Once a schema is defined, validation is applied using two transformers in sequence:

1. **Set the entity type** –– assigns the correct entity schema to the incoming data.
2. **Validates the entity type** –– checks the data against the schema rules.

Data that matches the schema passes through and continues processing. Data that does not match is filtered out and does not create a task.