> 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.md).

# Connection Mapping

Connections give Heeler raw inventory — *here's our GitHub org, here's our AWS accounts, here are our clusters.* **Connection Mapping** is where you tell Heeler the *meaning* of those connections — which repos belong to which application, which cloud accounts are production vs staging, who owns what, and how tickets should flow.

Getting Connection Mapping right is the single biggest lever for downstream quality. Routing, prioritization, dashboards, and workflows all depend on it.

### Where to find it

Open the **gear icon** in the top-right → **Connection Mapping** tab.

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

### What's here

| Sub-section  | What it's for                                                        |
| ------------ | -------------------------------------------------------------------- |
| Teams        | Define teams and their default ticket/notification settings.         |
| Applications | Group repositories and services into logical applications.           |
| Environments | Tag cloud accounts and clusters as production / staging / dev / etc. |
| Ticketing    | Per-team ticket project, type, and routing configuration.            |

### Quick start

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

### Why this matters

Connection Mapping powers:

* **Routing** — workflows know which team to notify or assign tickets to.
* **Prioritization** — Heeler weighs findings on production assets higher than non-production.
* **Reporting** — dashboards roll up by team and application.
* **PR feedback** — comments and fix PRs are scoped to the right owners.


---

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