> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/virtual-environments/accessing-virtual-environments/the-anatomy-of-a-virtual-environment.md). # The anatomy of a virtual environment ## Introduction Having selected a virtual environment from the [overview](/product-documentation/virtual-environments/accessing-virtual-environments/understanding-the-virtual-environments-overview-page.md) page, setup information and options are available over a series of panels:

## Available information & options

#	Panel	Summary
1	General	General details (provided when you created the environment) can be updated here. The given `name` is displayed to users throughout the dashboard, wherever virtual environments can be selected. The `type` can be set to `test` or `live`. Your selection here has no functional impact; however, you can filter environments based on this value from the overview page. Any existing labels (defined for process flows or other virtual environments) are available for selection, or you can use the `create label` option to add new ones. For general information about working with labels, please see our Label management page. If needed, you can change any of these details and click the `update` button to confirm.
2	Configuration versions	A virtual environment `version` is where you configure which process flow components (connector instances, caches, scripts, etc.) to replace when flows are run for this environment. A `draft` version is generated when a virtual environment is created - use this to configure all required replacements for process flows that you intend to deploy to this environment. As your draft moves through the version lifecyle, further versions are added to this list. For more information, please refer to Understanding virtual environment versions.
3	Package deployments	A package is a collection of process flows that can be deployed to a virtual environment in one action. Any packages that are deployed to this environment are shown here. For more information, please refer to our Virtual envrionment packages section.
4	Flow deployments	When a process flow version is deployed to a virtual environment, it's shown in the `flow deployments` panel. Here you can see which flow version was deployed, when this was done, and (if applicable) the associated package. You can deploy multiple process flows to a single virtual environment; however, there can only be ONE version of each process flow in any given virtual environment. Options are available to enable/disable or delete flow version deployments in this panel. If a flow deployment is deleted, the corresponding entry is removed from this list. Otherwise, deployments remain for all time. For more information, please refer to Deploying a process flow to a virtual environment.
5	Details	In the top-right corner, you'll find a label showing the environment type (test or live), together with creation details and a URL prefix. You'll need the URL prefix if you're creating/deploying process flows with webhook/callback triggers, or our API.

{% hint style="info" %} Check the ellipsis icon associated with items in these panels for possible actions - for example:

{% endhint %}