---
title: "Deploy a Configuration to a Test Environment"
slug: "deploy-a-configuration-to-a-test-environment"
description: "Describes how to deploy the content of the Lasernet workspace to a test environment."
tags: ["Configuration", "Deploy", "Lasernet Core", "Workspace"]
updated: 2026-05-26T14:53:21Z
published: 2026-05-26T14:53:21Z
canonical: "kb.lasernetgroup.com/deploy-a-configuration-to-a-test-environment"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy a Configuration to a Test Environment

**Applies to:** Lasernet Core 11

After you make changes to a Lasernet Core configuration, you will typically need to test that your changes work as you intend them to. To do this, you can use Deploy Workspace to deploy the configuration to a test Lasernet Core environment.

Deploy Workspace sends the configuration from the [“workspace”](/v1/docs/synchronize-configuration-updates-between-lasernet-developers-workspace) to a selected test environment. This includes the latest, in-progress, uncommitted changes to the configuration.

> [!NOTE]
> Note
> 
> To “deploy” a configuration means to send it to a Lasernet Core environment, which will run the configuration.

> [!TIP]
> Tip
> 
> Before you deploy the configuration to the test environment, [ensure that you have saved all essential resource files to the workspace](/v1/docs/synchronize-configuration-updates-between-lasernet-developers-workspace#save-resources).

> [!NOTE]
> Note
> 
> For Lasernet Core 10 documentation about “patching” a server, see the [Lasernet Config Server and Deployment Guide](/v1/docs/lasernet-config-server-and-deployment-guide).

## Deploy Workspace

To deploy the workspace to a test Lasernet Core environment, follow these steps:

1. In Lasernet Developer, [open the configuration](/v1/docs/create-or-import-a-configuration) that you want to deploy for testing.
2. In the Lasernet Developer toolbar, click **Deploy Workspace** (see 1 in the image below).

![A number annotated screenshot that supports instructions on how to deploy the workspace to a test environment](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/deploy workspace.png)
3. In the **Deploy workspace configuration** window, select the checkbox (2) for the test environments that you want to deploy the workspace to.
4. Click **Ok**. Lasernet Developer displays a progress bar for the deployment.
5. After Lasernet Config Server has deployed the configuration, click **Close**.

In Manage, the **Deployment History** area of an environment’s properties pane displays **Revision: Workspace** in the top (most recent) history item if that environment currently has the workspace deployed to it (instead of a configuration revision).

![A rectangle indicates the Revision: Workspace property value for the most recent deployment history item for an environment.](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/deploy workspace(1).png)

In the Lasernet Config web app, on the **Environments** page of the Lasernet Config web app, the **Revision** column contains **Workspace** for any environment that currently has the workspace deployed to it (instead of a configuration revision).

![The Environments page of the Lasernet Config web app containing an environment that contains Workspace in the Revision column](https://cdn.document360.io/c831ef63-c6b3-48ee-b443-3e33644e4e2e/Images/Documentation/workspace deployed to environment in lasernet config app.png)