# Flow deployment

## Introduction

Having built or updated a process flow, it must be deployed and enabled before it runs automatically, according to defined [trigger shape](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape) settings (or [API requests](https://doc.wearepatchworks.com/product-documentation/developer-hub/patchworks-core-api)). How you do this depends on whether the [virtual environments](https://doc.wearepatchworks.com/product-documentation/virtual-environments/about-virtual-environments) feature is enabled for your company profile. 

* If yes, you have the option to deploy any version of a process flow to multiple environments, or to `no environment`. You do this via the `view deployments` modal within process flow settings. For details, please refer to [Deploying a process flow (with virtual environments)](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/flow-deployment/deploying-a-process-flow-with-virtual-environments).
* If no, you will only ever deploy a draft or inactive version of a flow, and you don't need to decide *where* this is deployed - by default, the deployment is made to `no environment`. For details, please refer to [Deploying a process flow (without virtual environments)](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/flow-deployment/deploying-a-process-flow-without-virtual-environments).

## How do I know if virtual environments are enabled?

If you're not sure whether virtual environments are enabled, check the left-hand navigation menu - if you see a `virtual environments` section, this feature is enabled:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FOFNhR2oxcMOKFeKuJLID%2Fcheck%20for%20virtual%20envs.png?alt=media&#x26;token=3ddb2ddf-15d2-47d4-8429-a956945c1545" alt=""><figcaption></figcaption></figure></div>

## Pages in this section

* [Deploying a process flow (with virtual environments)](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/flow-deployment/deploying-a-process-flow-with-virtual-environments)
* [Deploying a process flow (without virtual environments)](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/flow-deployment/deploying-a-process-flow-without-virtual-environments)