---
title: "Environment Types"
slug: "environment-types"
description: "Configure Environment Types in Decisions Deployment Tower to define development, testing, staging, and production environments used for deployment planning, package promotion, and release management."
updated: 2026-08-31T20:47:18Z
published: 2026-08-31T20:47:18Z
canonical: "documentation.decisions.com/environment-types"
---

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

# Environment Types

## Overview

Environment Types define the role of each Decisions environment connected to the Deployment Server. Each environment type serves a specific purpose in the deployment process and is identified using environment-specific tags during registration.

The Deployment Server supports three environment types: **Development**, **QA**, and **Production**. Development supports a single instance, while QA and Production support multiple instances.

NoteAll environments connect to the Deployment Server using secure authentication keys. A separate key is generated for each environment instance during registration.  
To help connect the deployment server, please refer to the article "[Connecting an Environment to the Deployment Server](/v10/docs/connecting-an-environment-to-deployment-server)".

---

## Development Environment

The **Development** environment is the source environment where users build, update, and check in project changes. Development is limited to a single instance.

The Development environment commonly supports the following activities:

- [PMIS integration](/v10/docs/pmis-configuration)
- [User Story](/v10/docs/user-stories) tracking
- [Sprint](/v10/docs/sprints) management
- Code check-in

ImportantDevelopment is the originating environment for every project change. Deployment types (Manual, Auto Deploy, Schedule Deploy) control how a [Deployment Package](/v10/docs/deployment-packages) is delivered to a target environment; only QA and Production are deployment targets. Because Development is never a deployment target, no deployment type applies to it.

---

## QA Environment

The **QA** environment is used to test and validate builds before they are promoted to Production. QA supports multiple instances, allowing teams to configure separate testing environments as needed.

The QA environment commonly supports the following activities:

- Unit testing
- UAT configuration
- Flexible deployment scheduling
- Build validation

### Deployment Types for QA

After a QA environment is connected to the Deployment Server, administrators can configure how deployments are delivered to that environment.

The following deployment types are available for QA environments:

- **Manual:** Builds are deployed only when a user manually starts the deployment.
- **Auto Deploy:** New builds are automatically deployed to the configured QA environment as soon as they are created in a Deployment Package.
- **Schedule Deploy:** A selected package is deployed automatically at a specified future date and time.

For QA environments that support automated deployment behavior, administrators can also configure the system to **run unit tests after deployment**.

Important Notes

- **Auto Deploy** is typically intended for non-production target environments such as QA.
- If a deployment is already scheduled and a user starts the deployment manually before the scheduled time, the scheduled deployment is canceled, and the deployment begins immediately.

---

## Production Environment

The **Production** environment is the live environment where finalized and approved packages are deployed. Production supports multiple instances.

The Production environment commonly supports the following activities:

- Final deployment
- Package promotion
- Version increment
- Release management

RecommendationProduction environments should use controlled deployment processes. Automatically deploying every new build to Production is not recommended.

---

## Navigating Between Environments (v10.2+)

Starting in **v10.2+**, Users can navigate between assigned environments using the Environment Type badge displayed in the Portal Header. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1788185250987.png)

## Feature Changes

| Description | Version | Release Date | Developer Tag |
| --- | --- | --- | --- |
| Users can navigate to assigned environments by clicking on the badge available in the portal. | 10.2 | September 2026 | [DT-047164] |

## Related Articles

- [Organizations](/v10/docs/organizations)