> For the complete documentation index, see [llms.txt](https://learn.heeler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.heeler.com/tenant-admin-guide/connection-mapping/environments.md).

# Environments

An **Environment** is the logical role a cloud account, project, subscription, or Kubernetes namespace plays — production, staging, development, sandbox, etc. Tagging this correctly is critical because Heeler weighs findings differently based on environment (a vulnerability exploitable in prod is treated as far more urgent than the same vulnerability in dev).

### Where to find it

Administration → **Connection Mapping** → **Environments** in the left sidebar.

URL: `https://app.heeler.com/administration/connection_mapping/environments`

### Cloud provider tabs

The page has tabs for each cloud provider you have connected:

* **Amazon Web Services**
* **Google Cloud Platform**
* **Microsoft Azure**
* **Kubernetes**

Each tab shows the accounts/projects/subscriptions/clusters available for mapping.

### Quick start

See the [Getting Started](/getting-started.md) > [Connection Mapping](/getting-started/connection-mapping.md) > [Environments](/getting-started/connection-mapping/environments.md) documentation. 

### Reference

#### What environment mapping affects

* **Risk prioritization** — findings on production assets are weighted higher.
* **Workflows** — can branch on environment ("only notify on prod findings").
* **Dashboards** — environment is a primary filter dimension.
* **Heeler Risk** — the priority model incorporates environment as a factor.

#### Kubernetes environments

For Kubernetes clusters, you typically tag the entire cluster as one environment. If you run a single multi-tenant cluster with prod and non-prod namespaces, environment mapping can be done at the namespace level — check your cluster setup details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.heeler.com/tenant-admin-guide/connection-mapping/environments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.