---
title: "ezgh flags envs"
description: "Environments: where flags are targeted, each with its own SDK keys."
---

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

# ezgh flags envs

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh flags envs <command>
```

Environments (production, staging) live in a project. Each flag has its own targeting in each one, and each has its own SDK keys. Environments are IAM resources: a policy can allow changing flags' targeting in staging but not production (flags.configs.update on fen\_&lt;id&gt;/\*).

Part of [`ezgh flags`](/cli/reference/flags).

## Flags

This command also takes the [global flags](/cli/reference#global-flags).

## Subcommands

| Command | Description |
| --- | --- |
| [`ezgh flags envs create`](/cli/reference/flags-envs-create) | Create an environment |
| [`ezgh flags envs delete`](/cli/reference/flags-envs-delete) | Delete an environment, its SDK keys and its targeting |
| [`ezgh flags envs get`](/cli/reference/flags-envs-get) | Show an environment |
| [`ezgh flags envs list`](/cli/reference/flags-envs-list) | List the project's environments |

Source: https://docs.ezghcloud.com/cli/reference/flags-envs/index.mdx
