> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/faq/environments.md).

# 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 %}