---
title: "Considerations for Opting into Test & Deploy"
slug: "test-deploy-opt-in-considerations"
description: "Evaluate if Test & Deploy in Pigment suits your needs with insights on managing changes, team readiness, and effective release management."
updated: 2025-05-30T13:47:12Z
published: 2025-08-22T10:56:55Z
---

> ## 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.

# Considerations for Opting into Test & Deploy

![](https://cdn.document360.io/e47cfe35-dc28-40c7-a083-6cf003073d8e/Images/Documentation/38ad0b6e-b580-41e2-be50-e8b2bdcf1b83.png)

This article is here to help you evaluate if Test & Deploy (T&D) in Pigment is the right fit for you. T&D is a powerful tool for managing changes, but setting it up requires careful consideration. Here are some considerations to keep in mind as you decide if T&D suits your needs and current setup.

## Managing Changes in Active Environments

**Consideration**: Multiple modelers are making changes that need to be deployed to environments where end users are actively working. As a result, these changes need to be managed or scheduled to avoid disruptions to operations.

**Pigment Advisory**: If modelers are working on Applications that are not yet in use by end users, consider if T&D is needed before these Applications go live. T&D is particularly useful when you need a structured release process to prevent operational disruptions.

## Team Readiness and Understanding of T&D Scope

**Consideration**: Every builder and administrator on our team understands the scope of T&D within Pigment, as well as their responsibilities for implementing lifecycle management for our business.

**Pigment Advisory**: When T&D is implemented, the main requester will receive access to the development, or Dev, Workspace for the managed Applications. This individual is responsible for ensuring that all other builders are added to the Workspace. Without this access, other builders will be unable to make further changes to their Applications. Aligning the team on this responsibility is important for successful implementation.

## Change or Release Management Plan

**Consideration**: Our team has an established change or release management plan for modelers.

**Pigment Advisory**: If your team has an existing change management plan, update it to incorporate T&D procedures. If not, consider developing one to support the structured implementation of T&D. This will help streamline the process and maintain control over the Applications’ lifecycle.

## Related Information

- [Introduction to Test & Deploy](/v1/docs/introduction-test-deploy)
- [Map Out Your Test & Deploy Environments](/v1/docs/map-out-your-test-amp-deploy-environments)
- [What Are Structural Changes in Test & Deploy?](/v1/docs/structural-changes-test-deploy)
- [Manage Data Changes in Dimension Lists](/v1/docs/dimension-list-data-changes)
- [About Deploying Changes in Test & Deploy](/v1/docs/about-deploying-changes-in-test-amp-deploy)
- [Full & Partial Deployment in Test & Deploy](/v1/docs/full-and-partial-deployment-in-test-amp-deploy)
- [Understand Test & Deploy for Pigment Features](/v1/docs/understand-test-deploy-pigment-features)

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>