> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/internal-developer-portal/use-idp/environment-management/get-started.md).

# Get Started with Environment Management

Welcome to **Getting Started with Environment Management**. This document will guide you through the environment management capabilities in Harness IDP. To understand the core features and key concepts of Environment Management in IDP, go to [Overview & Key Concepts](/internal-developer-portal/use-idp/environment-management/overview.md).

An environment is a collection of software services deployed using CD and executed on infrastructure provisioned through IaCM. Environment Management provides **developers** with a self-service way to create and manage environments, while **platform engineers** define the standards behind them. Together, these modules ensure that every environment is consistent, secure, and easy to use.

![](/files/GCOBD09r2HrelBLL3b0b)

### How environment management works for you <a href="#how-environment-management-works-for-you" id="how-environment-management-works-for-you"></a>

* **Platform Engineers** - You can design and maintain Environment Blueprints. A blueprint is a declarative YAML template that defines which infrastructure resources (IaCM workspaces) and services (IDP Catalog components) make up an environment, how they depend on each other, and how they are provisioned and torn down. Before creating a blueprint, platform engineers set up the underlying resources in Harness: workspace templates in IaCM, CD services, and deployment pipelines. These are then referenced in the blueprint YAML. Go to [Create an Environment Blueprint](/internal-developer-portal/use-idp/environment-management/blueprints/create-environment-blueprint.md) to get started.
* **Developers** - You can create environments from blueprints your platform team has published. You select a blueprint, provide the required inputs (such as a name or service version), and the system provisions infrastructure and deploys services in the correct dependency order. Go to [Environments](/internal-developer-portal/use-idp/environment-management/environments.md#create-environments) to create your first environment.

***

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

Use the checklist below to ensure your setup is complete before getting started.

#### Required Harness modules <a href="#required-harness-modules" id="required-harness-modules"></a>

* **Internal Developer Portal (IDP)** - For environment blueprints and catalog
* **Continuous Delivery (CD)** - For service deployments
* **Infrastructure as Code Management (IaCM)** - For infrastructure provisioning

#### Required feature flags <a href="#required-feature-flags" id="required-feature-flags"></a>

Enable these feature flags in your Harness account:

* `PIPE_DYNAMIC_PIPELINES_EXECUTION` - Dynamic pipeline execution. [Click here](/harness-ai/use-harness-platform/pipelines/dynamic-execution-pipeline.md) to learn more.

#### Infrastructure requirements <a href="#infrastructure-requirements" id="infrastructure-requirements"></a>

* Infrastructure with Harness Delegate installed
* [Cloud provider connector](/harness-ai/use-harness-platform/connectors/cloud-providers.md) configured (GCP, AWS, or Azure)
* Kubernetes connector for the target cluster
* Git connector with API access (for storing manifests and state)

For more details on how to configure connectors, visit [Connectors](/harness-ai/use-harness-platform/connectors.md)

#### Secrets & secret manager <a href="#secrets-and-secret-manager" id="secrets-and-secret-manager"></a>

* Ensure **Harness Secret Manager** is enabled in your account. Environment Management uses it to store some system-generated keys. Go to [Harness Secret Manager Overview](/harness-ai/use-harness-platform/secrets/secrets-management/harness-secret-manager-overview.md) to learn more.
* If Harness Secret Manager is not enabled, create a secret `IDP_PO_API_KEY` in the same project where environments will be created. The secret must contain a Service Account Token with the following IaCM Workspace permissions: `Create`, `Update`, and `Delete`. This ensures the token has exactly the permissions needed to manage IaCM Workspaces in that project.

#### Permissions <a href="#permissions" id="permissions"></a>

Click below to view the permissions you would require for each area: IDP, CD, and Platform.

{% tabs %}
{% tab title="IDP Permissions" %}
Permissions required to manage entities within the IDP

| Resource                  | Permissions                     |
| ------------------------- | ------------------------------- |
| IDP Environment           | `View` `Create` `Edit` `Delete` |
| IDP Environment Blueprint | `View` `Create` `Edit` `Delete` |
| IDP Catalog               | `View` `Create/Edit` `Delete`   |
| {% endtab %}              |                                 |

{% tab title="CD Permissions" %}
Permissions required for managing CD resources.

| Resource     | Permissions                             |
| ------------ | --------------------------------------- |
| Pipeline     | `View` `Create/Edit` `Delete` `Execute` |
| Service      | `View` `Create/Edit` `Delete` `Access`  |
| Environment  | `View` `Create/Edit` `Delete` `Access`  |
| {% endtab %} |                                         |

{% tab title="Platform Permissions" %}
Permissions required for managing platform-level configurations and shared resources.

| Resource      | Permissions                                   | Notes                                                                                                                 |
| ------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Connector     | `View` `Create/Edit` `Delete`                 | If using a Harness managed code repository for Git based configuration, repository level access may also be required. |
| Secrets       | `View` `Create/Edit` `Delete`                 |                                                                                                                       |
| Templates     | `View` `Create/Edit` `Delete` `Access` `Copy` |                                                                                                                       |
| Delegates     | `View` `Create/Edit` `Delete`                 | Required if delegates are used with connectors.                                                                       |
| {% endtab %}  |                                               |                                                                                                                       |
| {% endtabs %} |                                               |                                                                                                                       |

Additionally, permissions in Cloud (AWS, GCP etc) to create and manage resources, workloads would be needed.

Once the setup is complete, additional users can be granted the required permissions within Environment Management. For more details, refer to the [RBAC section in the Environment Management Overview](/internal-developer-portal/use-idp/environment-management/overview.md#rbac-for-environment-management).

***

### Tutorials <a href="#tutorials" id="tutorials"></a>

| Name                                                                                                                                              | Description                                                                                                                                                          |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Tutorial 1 - Build an Ephemeral Developer Testing Environment](/internal-developer-portal/use-idp/environment-management/tutorials/tutorial1.md) | Set up a self-service ephemeral environment system that automatically provisions isolated test environments for PRs and deletes them after a stipulated time period. |

***

### Quick start path <a href="#quick-start-path" id="quick-start-path"></a>

If you are setting up environment management for the first time, follow this sequence:

1. **Platform Engineers**: [Create an Environment Blueprint](/internal-developer-portal/use-idp/environment-management/blueprints/create-environment-blueprint.md) to define the infrastructure and service template for your team's environments.
2. **Developers**: [Create an Environment](/internal-developer-portal/use-idp/environment-management/environments.md#create-environments) using an available blueprint.
3. Manage the environment lifecycle from the [Environments](/internal-developer-portal/use-idp/environment-management/environments.md) page, including starting, stopping, updating, and deleting environments.