> For the complete documentation index, see [llms.txt](https://umber.gitbook.io/umber/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://umber.gitbook.io/umber/concepts/environments.md). # Environments An **environment** is the logical space you deploy asset versions into — typically mirroring your software environments, like `dev`, `staging`, and `prod`. Every environment has an **Environment ID**, which shows up directly in delivery URLs: ``` https://adn.umbercloud.io/api/va//// ``` ## Why environments matter Environments are what let you stage a new asset version safely: * You can set a version **Live** in `dev` while `prod` continues serving the previous **Default** version — no file renaming, no code changes on either side. * The [Umber CLI](/umber/cli-tools/umber-cli.md) reads and writes this same `env` value (`--env`, default `dev`) when migrating or uploading assets, so CLI-driven and dashboard-driven deployments target the same environments consistently. * Because a version isn't duplicated per environment (see [Zero Redundancy](/umber/why-umber/zero-redundancy.md)), promoting a version from `dev` to `prod` doesn't mean copying the underlying file — only the environment's pointer to it changes. Within an environment, each version is Live, Offline, or not deployed there at all, and at most one Live version is the environment's current default — see [Deployment States](/umber/concepts/deployment-states.md) for what each of those means and how they relate. ## Creating an environment From the dashboard **Home** page, choose **Create New Environment** and provide an Environment ID, Name, and optional description. See the [Quickstart](/umber/getting-started/quickstart.md) for the full walkthrough. `actions` is reserved and can't be used as an Environment ID. Since the Environment ID appears in every delivery URL, pick something short and stable — it can't be changed once the environment exists. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://umber.gitbook.io/umber/concepts/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.