> For the complete documentation index, see [llms.txt](https://bluebricks.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluebricks.co/docs/orchestration/collections/properties.md).
# Properties
## Overview
Collection properties supply values like regions, naming conventions, or account-specific defaults that automatically flow into every [blueprint](https://github.com/bluebricks-dev/Bluebricks-Documentation/blob/main/orchestration/packages/creating-blueprints/README.md) deployed to the collection.
## How collection properties work
When a blueprint property key matches a collection property name, the collection's value is injected automatically. You define values once at the collection level, and every environment inherits them.
* Collection properties override defaults defined in the blueprint, ensuring consistent values across environments
* If a property is marked as **enforced**, environments must use that exact value (e.g., forcing all resources into `eu-west-1`)
* Properties can reference dynamic values like `${{bricks.collection.slug}}_${{bricks.environment.id}}`
{% hint style="info" %}
Enforced properties are hard-coded values. If not enforced, they act as defaults that environments can override.
{% endhint %}
## How to set properties
1. Navigate to the desired collection page
2. Select **Properties** from the left side menu
3. Click **Add property**
4. Enter the name (key) and value
5. (Optional) Toggle **Enforced** to lock the value
6. Click **Save**
To delete a property, click the three-dot menu on the property row and select **Delete**.