Local deployment supports deploying changes between Applications in the same Workspace using a familiar Test & Deploy (T&D) experience. You do not need T&D configured in your environment to perform a local deployment.
It is typically used in Development (Dev) or Production (Prod) environments to support more targeted updates and synchronization outside of the standard T&D workflow.
Access rights and permissions
⚠️ Important
Local deployment is available by default for Enterprise customers with granular deployment.
To run a local deployment, you must have the required permissions in both the source and target Applications.
To use Edit in copy or Configure a local deployment group with managed T&D Applications in source or target environments, a Security Admin must turn on Allow local deployment on managed Applications in this Workspace in Workspace Security settings.
What is local deployment?
Local deployment can work in any Workspace. For T&D-enabled Workspaces, it is meant to be used primarily in Dev or Prod environments. It is not commonly used in Test environments, as these typically serve as transitional environments for managed Applications.
Local deployment provides a lightweight, flexible alternative to the full T&D workflow by supporting safe changes through temporary copies and controlled deployments within a single environment. It enables deployments between Applications within the same Workspace.
Common use cases include:
Safer development workflows. In Dev, local deployment enables multiple contributors to work on copies of the same Application within a single Workspace. It supports isolated testing by allowing users to create a copy of an unmanaged Application, make and validate changes independently, and deploy selected updates back to the source Application, protecting live data from risky or experimental changes.
Rapid production fixes and controlled updates. In Prod, local deployment is helpful when issues cannot be reliably reproduced in Dev due to model or data differences. It enables rapid resolution by allowing users to duplicate a live Application with the same model version and data, investigate or fix the issue safely in the copy, and deploy only the required changes back to the original Application without going through the full T&D workflow. Changes made directly in Prod may need to be replicated in Dev to avoid inconsistencies.
Recovery and targeted fixes. An Application can be recovered from backup to apply fixes, then deployed back to the live version using local deployment.
How to run a local deployment
There are two ways to start a local deployment:
Edit in a copy. Best for quick fixes and updates using a guided workflow with temporary Application copies.
Configure a local deployment group. Best for setting up reusable custom source and target mappings for more controlled and flexible deployments.
Edit in a Copy
To start a local deployment, go to an Application in your Workspace:
Select the three dots on the Application.
Select Edit in a copy
Select Get Started.
Select up to five Applications from the drop-down menu to create temporary duplicates. Rename them so they are easy to identify.
Select Duplicate.
Name the temporary Applications group to make it easy to identify and apply your changes later, then select Duplicate. This name appears in the Application label. This automatically creates an uneditable deployment group on your local deployment page.
⚠️ Important
During a local deployment, the original Application is frozen while the duplicate is created. Only one active copy of an Application is allowed at a time.
Make your changes to the duplicated Application, then select the three dots on one of the duplicate Applications.
Select Deploy changes to deploy changes back to the live Application.
From the Changes to deploy page, select Add changes, then review and select the changes to deploy. You can then perform a granular deployment back to the original target Application and review all deployments from Deployments in the sidebar. For more information, see Granular Deployment in Test & Deploy.
Once the deployment is complete, it is best practice to delete the Application copy so a new one can be created. If the duplicate Application has not been deleted, you can select Deploy changes to start another deployment.
Custom deployment group
You can configure a local deployment group in your Dev or Prod environment to deploy changes between Applications, mapping source and target Applications to ensure safe, consistent deployments.
Source Application. A source can be a live or recovered Application, and can be managed or unmanaged.
Target Application. A target must be a live and unmanaged Application.
⚠️ Important
An Application cannot serve as both source and target within the same deployment group. Live and recovered sources cannot be mixed. If any selected source is a recovered Application, all sources must be recovered.
To configure a deployment group:
Go to Workspace Settings.
Select Local deployment.
Select + New deployment group.
In the Create a new deployment group screen, give the deployment group a unique name.
Under Configuration, select the source and target Applications from the dropdown menu. You can choose from live or recovered Applications in the source dropdown menu.
Select Add Application to add another configuration.
(Optional) Toggle off Include Calendar data if you don’t want to include this in your deployment.
Select Save to save your deployment group.
View and manage local deployment groups
You can view and manage all deployment groups from the Local deployment page.
To view existing deployment groups:
Go to Workspace Settings.
Select Local deployment to view all existing deployment groups. You can view the Source and Target (original) Applications associated with each group.
Edit a deployment group
To edit a custom deployment group:
On the Local deployment page, hover over the three dots.
Select Edit and make your changes.
Select Save.
ℹ️ Note
Deployment groups created through the Application menu using Edit in a copy can’t be edited from the Local deployment page and can only be deleted.
Delete a deployment group
ℹ️ Note
Deleting a deployment group does not delete any Applications, only the associated deployment configuration.
You can delete automatically and manually created deployment groups from this page.
To delete a deployment group:
On the Local deployment page, hover over the three dots.
Select Delete.