---
title: "Granular Deployment in Test & Deploy"
slug: "granular-deployment-in-test-and-deploy"
description: "Learn how to use Granular Deployment in Pigment’s Test & Deploy to deploy specific structural changes between environments while automatically managing dependencies."
tags: ["granular deployment"]
updated: 2026-05-25T17:14:36Z
published: 2026-05-25T17:14:36Z
---

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

# Granular Deployment in Test & Deploy

Granular deployment allows you to test and deploy individual changes within an Application and dependent Applications, rather than deploying all changes at once. This gives you more control and flexibility, so you can choose exactly which changes to move to the target environment.

This article covers granular deployment, including how it works, how to manage deployments, and its impact on environments.

> [!CAUTION]
> 🛡️**Warning**
> 
> Full deployment is unavailable when granular deployment is turned on in an environment.

For more information on Test & Deploy, including how it works and how environments are structured, see [Introduction to Test & Deploy](/v1/docs/introduction-test-deploy).

## Access rights and permissions

You must have the following rights and permissions to use granular deployment:

- You have equivalent permissions in both the source and target environments.
- You have access to all Applications involved in the deployment (both deploying and receiving changes).

## Deployment options

Test & Deploy supported two deployment options:

- **Full deployment.** Deployed all changes across all Applications in the Workspace from a source to a target environment.
- **Partial deployment.** Deployed changes from selected Applications, along with their dependencies, from a source to a target environment.

Granular deployment introduces a new deployment option, giving you more control over what is deployed between your environments.

## What is granular deployment?

Granular deployment allows you to deploy specific selected changes without deploying an entire Workspace or Application. It provides more precision and control when deciding what to move from a source to a target environment.

You can access deployment options from the top-right corner of your Dev or Test environment.

> [!WARNING]
> ⚠️ **Important**
> 
> Deleted Applications can be included in either deployment option but only for full deployment.

The following options are available:

- **Deploy entire Applications****.**Choose one or more Applications to deploy.
- **Deploy granular changes****.** Choose specific changes for a more detailed, granular deployment.

![User interface showing deployment options and application management features for business planning.](https://cdn.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/Images/Documentation/KB - Granular Deploy-1.png)

> [!WARNING]
> **⚠️ Important**
> 
> Deploying from within an Application or from the Application menu always opens the granular deployment option.
> 
> Full Application deployment is only available from the **New deployment**button on the Workspace homepage.

## Manage dependencies in granular deployment

With full and partial deployment in Test & Deploy, changes were deployed at the Application level. If a change depended on elements in another Application, those Applications had to be deployed together.

Granular deployment introduces change-level selection. No changes are selected by default. You review detected structural changes and explicitly choose which ones to deploy. If a selected change has dependencies, they are clearly indicated by required or optional labels:

- **Required**. These changes are strictly required for the deployment. Required dependencies are automatically included and cannot be removed. Dependencies from other Applications are included only when necessary. Unrelated changes remain excluded.
- **Optional**. These changes are not strictly required for the deployment but are automatically selected and can be deselected.

If you remove a selected change with *Optional* dependencies, its associated dependencies are updated accordingly.

This allows you to deploy a single structural update, such as a Metric, Dimension, or List Property, without deploying other in-progress changes in the same Application, while ensuring the deployment remains valid even for cross-Application dependencies.

## Run a granular deployment

To start a granular deployment:

1. On the Workspace homepage, select **New deployment**
2. Choose **Deploy granular changes****.**
  1. *(Optional) Y*ou can select **Deploy changes Source → Target** to deploy changes from the Application menu.
3. In the **Start a new deployment** panel, select the Applications with changes you want to deploy from the drop-down menu. Dependencies are automatically included.
4. *(Optional)*Turn on **Add deleted Applications to the scope** to include deleted Applications alongside granular changes. Deleted Applications are always deployed in full.
5. *(Optional)*Turn on **Include Workspace settings to the scope** to include User Groups in the deployment.

User Groups can only be deployed using a granular deployment.
6. Select **Next step: Review changes.** This takes you to the **New deployment** page.

![Deployment interface showing changes for Workforce Planning with options to add changes.](https://cdn.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/Images/Documentation/KB - Granular Deploy-02 (1).png)

From the **New deployment** page:

1. From the sidebar, select the Application containing changes to deploy under **Selected scope**.

> [!NOTE]
> ℹ️ **Note**
> 
> Before granular deployment, the Diff screen automatically displayed changes to Applications in the Workspace, including updates, removals, creations, and their dependencies. The Diff screen now remains empty until you select the changes you want to deploy.

1. Select **Add changes**, followed by **Review & select changes**.
2. **Use the filters** to search for a change or filter changes by type, Boards & Sequences, Blocks, or review them manually.
3. Select a change to open the **Change details**panel, where you can view information about the individual change, including any required or optional dependencies.
4. *(Optional)*If dependencies are listed, select **Show changes** to expand them. Select a dependency name to view its details in its associated Application.
5. **Toggle** any change to **On** to select specific changes to deploy to the target environment.
6. Select **Add selected changes** or **Cancel** to return to the previous screen.
7. From the **Changes to deploy** screen, select **Deploy X changes** to deploy selected changes or select **+ Add changes** to review and add more changes to the scope.
8. In the **Summary** panel, add a name and description for the deployment and review the deployment scope.
9. Select **Deploy** then select one of the following options to complete the deployment:
  1. **Lock all Applications**. Select this option to lock all managed Applications in your source and target environments. This is the most secure way to ensure that no changes can affect the deployment.
  2. **Lock X Application**. Select this option to lock only the deployed Applications in your source and target environments. This flexible option increases the risk of deployment failure if another Member uses or updates shared Blocks from an unlocked Application during the deployment process.

![Overview of changes in workforce planning, including added and deleted elements.](https://cdn.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/Images/Documentation/KB - Granular Deploy-04 (1).png)

## **Manage deployments**

Members who have deployment notifications turned on are notified once the deployment is complete. Notifications can be sent for the source environment, the target environment, or both, depending on individual settings.

> [!NOTE]
> ℹ️ **Note**
> 
> If you have feedback or experience any issues, [please contact our Support team.](https://support.pigment.com/)

To manage your organisation’s deployments, go to the **Production Workspace** homepage and select **Deployments**.

This page lists all deployments, including:

- A summary of the deployment
- Deployment scope (local, environment or data refresh)

> [!NOTE]
> ℹ️ Note
> 
> To perform a data refresh, [please contact our Support team.](https://support.pigment.com/)
- Number of changes and applications affected
- Required follow-up actions
- Deployment status and progress
- Deployment date and time
- The Member who deployed the changes

![Overview of deployment changes and updates for various applications in the organization.](https://cdn.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/Images/Documentation/KB - Granular Deploy.png)

## Workspace deployment notifications

Turn on Workspace deployment notifications to receive alerts when Application updates are deployed between environments. Email and Slack deployment notifications are turned off by default and can be enabled independently.

Members who enable deployment notifications receive a notification once a deployment is complete. Notifications can be enabled for:

- The source environment
- The target environment
- All environments

### Turn on deployment notifications

1. In your Workspace, go to **Settings** in the sidebar.
2. Under **Account Settings**, select **Notifications**.
3. Tick the checkbox next to **Deployments**.

> [!NOTE]
> ℹ️ Note
> 
> Deployment notifications are separate from Application notifications. To receive notifications about Snapshots, duplications, and recovered Applications, tick the checkbox next to **Workspace & Application operations** on the same page for each environment.

## Pigment Features supported in granular deployment

Granular deployment supports most Pigment features, with the exception of Scenarios, Automations and Integrations. If you notice any issues or have feedback, please [contact our Support team](https://support.pigment.com/).