# Understanding the virtual environments overview page

## Introduction

Virtual environments can be [viewed](#viewing-a-virtual-environment), [created](#creating-a-virtual-environment), and [managed](#managing-a-virtual-environment) from the `overview` page:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FT0DFuC3x2jdQ3Nd8YHaj%2Fvirtual%20environments%20overview%20page%20250820.png?alt=media&#x26;token=363f35d1-f5ba-46b6-8e57-65e7e76d408e" alt=""><figcaption></figcaption></figure></div>

Here you'll find all existing virtual environments, with [related information and options](#available-information-and-options).&#x20;

## Available information & options

<table><thead><tr><th width="83.671875">#</th><th>Summary</th></tr></thead><tbody><tr><td>1</td><td>Shows the number of deployed virtual environments from your total allowance. A virtual environment is considered to be <code>deployed</code> when it includes at least one process flow deployment, irrespective of whether that deployment is <a href="../managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/disabling-or-enabling-a-process-flow-deployment-for-a-virtual-environment">enabled or disabled</a>.<br><br>If you have a virtual environment that's no longer used, you should remove any associated flow deployments to ensure that it's no longer considered as 'deployed' for your allowance count. <br><br>Your allowance is determined by your <a href="../../getting-started/subscription-tier-limits">Core subscription tier and associated bolt-ons</a>.  </td></tr><tr><td>2</td><td>Existing virtual environments are shown as tiles in the main display area. Each tile includes <a href="#virtual-environment-tile-summaries">summary information</a>, so you can see the current status and related details.</td></tr><tr><td>3</td><td><p>If you have lots of virtual environments, it can be useful to filter those displayed by type, status, and/or labels:<br></p><p><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FjFBRzuiE9ERYZRIgT1Ax%2Fve%20filter%20options.png?alt=media&#x26;token=e910a8c4-c093-40a7-a49b-e076290904f4" alt=""></p><p> <br>You can also search for virtual environments by name.</p></td></tr></tbody></table>

## Virtual environment tile summaries

Each tile displays summary details for the virtual environment:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FBzLc5GFI2p5cRi2ykIld%2Fvirtual%20environment%20tile%20b%20250820.png?alt=media&#x26;token=e751eb34-026d-4be3-b63e-63308ffb7dc3" alt="" width="563"><figcaption></figcaption></figure></div>

Available information is summarised below:

<table><thead><tr><th width="83.671875">#</th><th>Summary</th></tr></thead><tbody><tr><td>1</td><td>The virtual environment name, as a hyperlink. Click the name to access the configuration for this virtual environment.</td></tr><tr><td>2</td><td>Access options to <a href="../managing-virtual-environments-versions-and-flows/managing-virtual-environments/deleting-a-virtual-environment">delete</a> or <a href="../managing-virtual-environments-versions-and-flows/managing-virtual-environments/duplicating-a-virtual-environment">duplicate</a> the virtual environment.</td></tr><tr><td>3</td><td>Lists all process flows currently deployed in the virtual environment. This list is limited to three displayed items. If more flows are present, you'll see a <code>+n more</code> marker, where <code>n</code> is the number of additional flows deployed in this environment. Hover your cursor over this indicator to view the names of these flows.</td></tr><tr><td>4</td><td>When creating a virtual environment, you select a <code>type</code> of either <code>test</code> or <code>live</code>. Your selection here has no functional impact; however, you can filter environments based on this value.</td></tr><tr><td>5</td><td>The number of versions (of any status) associated with this virtual environment. A virtual environment is only 'active' (i.e. available for <a href="../implementing-virtual-environments/deploying-a-single-process-flow-to-a-virtual-environment">flow version deployments</a>) when a deployed version is present.</td></tr><tr><td>6</td><td>A virtual environment is marked as <code>deployed</code> when it (a) includes a <a href="../implementing-virtual-environments/deploying-the-configuration-for-a-virtual-environment">deployed virtual environment version</a> AND (b) includes at least one <a href="../implementing-virtual-environments/deploying-the-configuration-for-a-virtual-environment">deployed flow version</a>. For more information, please see <a href="../implementing-virtual-environments/configuring-a-virtual-environment-version/understanding-virtual-environment-versions">Understanding virtual environment versions</a>.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://doc.wearepatchworks.com/product-documentation/virtual-environments/accessing-virtual-environments/understanding-the-virtual-environments-overview-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
