# Managing environments

<Frame>
  <img src="https://files.buildwithfern.com/https://webflow.docs.buildwithfern.com/15f4ce278e763bd111bd8b9576b7b582a3990d0c712a01de5120e4a3645e129c/products/webflow-cloud/pages/introduction/assets/environment-dashboard-05-20.png" alt="Environment dashboard" />
</Frame>

## Creating environments

When you create a Webflow Cloud project, you'll be prompted to add your first environment. You can create additional environments (like staging and development) to support your development workflow.

**To set up additional environments:**<br />

* In Webflow Cloud, select your project name to open the Environments Dashboard.
* Click “Create New Environment.”
* Select the GitHub branch you want this environment to track.
* Define the mount path (URL path) for your environment.
* Click Create Environment.

Every push to the selected branch will trigger a deployment to this environment.

## Mount paths

Each environment is assigned a unique URL path under your Webflow domain. When you deploy to an environment, your application becomes accessible at its designated path. This path-based routing allows you to:

* Host multiple environments under a single domain
* Maintain separate URLs for staging, development, and production versions
* Seamlessly integrate with Webflow's existing routing system

Mount paths are unique to each environment and are used to route traffic to the correct environment. Each mount path must be unique across all environments within a project.

## Changing mount paths

If you've already deployed an environment to your site with a mount path and you want to change it, you should:

* Click the ellipsis icon “...” for the environment
* Select "Edit"
* Change the mount path to your desired new path and save the changes
* **Publish your Webflow site**
* Trigger a deployment to the environment to propagate the mount path change

## Route conflicts

If a route conflict occurs between your Webflow Cloud application and your Webflow site, the Webflow Cloud application route takes precedence.

For instance, if you have a Webflow site at `mydomain.com` with the following:

1. A Webflow Cloud app mounted at `/users`
2. A Webflow page also created at `/users`

When a user visits `mydomain.com/users`, they will see the Webflow Cloud app, not the static page on your Webflow site.

To avoid conflicts:

* Choose mount paths that don't conflict with existing or planned Webflow pages
* Consider using distinct paths like `/app` for your Webflow Cloud applications
* Document your app routes to prevent future conflicts when creating new Webflow pages

## Edit an environment

* Click the ellipsis icon “...” next to the environment.
* Select Edit.
* Modify the mount path or other details.
* Save your changes.
* **Re-publish** your site to reflect updates.

## Unpublish an environment

To remove the environment from your domain entirely, you must delete the Webflow Cloud project **and** republish the Webflow site.

**Deleting the environment by itself doesn't remove it from your domain.**

## Delete an environment

Delete an environment to remove it from Webflow Cloud。 Deleting an environment doesn't delete the GitHub branch. Conversely, deleting a GitHub branch doesn't delete the environment - you must delete the environment manually from the dashboard.

* Click the ellipsis icon “...” next to the environment.
* Select Delete.
* Confirm the deletion.

<Warning>
  To remove the environment from your domain entirely, you must delete the Webflow Cloud project **and** republish the Webflow site.
</Warning>

<Warning>
  If you delete a GitHub branch, the associated environment won't automatically be deleted. You must remove it manually from the dashboard.
</Warning>

<Warning>
  Deleting an environment permanently removes all deployments associated with it.
</Warning>

## Access control and permissions

Anyone with access to your deployed mount path can view the environment. For example, if deployed to /staging, anyone with the URL can access the staging version of your site.