# Environments ### Overview Environments are a way of mapping a cluster to an abstraction called as an environment. Ozone segregates this so that certain teams have access to specific environments, thus preventing any proverbial "cross-talk" during deployments which might result in an erroneous deployment to an environment that a team does not have access to. In addition, Ozone automatically picks up variables that are defined in the ci/cd workflows and maps them to the environment that the application is being deployed to, all done securely through Ozone's secret management for CI/CD {% hint style="info" %} When you create a cluster, ensure that it is mapped to an environment. And when an environment variable is defined, you have the freedom to define its value as per each environment {% endhint %} --- # 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://docs.ozone.one/ozone-end-user-guide/faq/environments.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.