# Using Context References ### Overview You can insert **dynamic references** into property values when configuring **collection properties** or **environment properties**. These references automatically pull information from the current **Environment** or **Collection**, so you don’t have to hard-code values. When the environment runs, the reference will be replaced with the actual value. ### Available References #### Environment References

Reference	Description	Example Output
`${{bricks.environment.slug}}`	The unique slug of the environment.	payments-prod
`${{bricks.environment.package}}`	The blueprint or package assigned to the environment.	@bluebricks/payments_blueprint
`${{bricks.environment.created_time}}`	The date/time the environment was created. (Only works for existing environments)	2025-06-30T09:27:14Z

{% hint style="danger" %} `${{bricks.environment.created_time}}` refers to the creation time of the parent environment and not to a specific run. This means every run of the same environment will have the same creation\_time. {% endhint %} #### Collection References

Reference	Description	Example Output
`${{bricks.collection.slug}}`	The unique slug of the collection.	prod
`${{bricks.collection.name}}`	The display name of the collection.	Production

### How It Works Anywhere you can type a property value, you can use: ``` ${{bricks.environment.*}} → Information about the environment ${{bricks.collection.*}} → Information about the collection ``` When the environment starts, these placeholders are replaced with the real values from your Bluebricks setup. ### **Example Usage** #### Collection **Properties Page** You can set a property to dynamically reference the collection name: ``` app_collection = ${{bricks.collection.name}} ```

When deployed to **Production** collection, this becomes: ``` app_collection = Production ``` #### Environment **Page** You can set a property to dynamically reference the environment name: ``` bucket_name = ${{bricks.environment.slug}} ```

When deployed the property will be resolved as: ``` bucket_name = single-tenant-452846-service-bucket ``` --- # 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://bluebricks.co/docs/orchestration/runs/using-context-references.md?ask= ``` 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.