> For the complete documentation index, see [llms.txt](https://coldbox-validation.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-validation.ortusbooks.com/overview/declaring-constraints.md).

# Declaring Constraints

Learn how to declare constraints for your data validation needs using cbValidation.

## What are Constraints?

A constraint is by definition the following:

> The state of being restricted or confined within prescribed bounds.

That is exactly what you will create for specific fields. You will declare the constraints for one or more fields. Each constraint will be composed of one or more **validators** and **validation data**. The validation data is defined by the validator and can be of `any` type, the default is an empty struct (`{}`)

```javascript
// Define the field by name
// The contents are the constraints
fieldName1 = {
    validator1 = validationData,
    validator2 = validationData
},

fieldName2 = {
    validator1 = validationData,
    validator2 = validationData
}
```

These constraints can then be defined in many locations where cbValidation can read them.

## Defining Constraints

You can define constraints in several locations:

1. [Configuration file](/overview/declaring-constraints/configuration-file.md)
2. [Inside a domain object](/overview/declaring-constraints/domain-object.md)
3. [A-la-carte](/overview/declaring-constraints/a-la-carte-via-event-handlers.md)

{% hint style="info" %}
When validating using `validate(), validateOrFail()` you have to specify a **target**, but specifying a **constraint** in your call is optional.
{% endhint %}

## Constraints Discovery

When you call the validation methods with **NO** `constraints` passed explicitly, then the validation module will discover the constraints using the following:

* Lookup your constraints in `myTarget.constraints` struct in your target object or struct.
* If you specify your constraint parameter as a **string**, the validator will lookup a shared constraint in your configuration file definitions.
* If you specify your constraint parameter as a **struct**, this struct will directly serve as your set of constraints, so you can specify your constraints on the fly, or specify an alternative set of constraints in your model, e.g `User.constraints` vs `User.signInConstraints`


---

# 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://coldbox-validation.ortusbooks.com/overview/declaring-constraints.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.