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

# Applications

## Grouping Repositories and Services into Logical Applications

An **Application** is a logical grouping of repositories / services that together form a deployable service, product, or surface. For example, a "Checkout" application might include a frontend repo, a backend repo, and a shared library repo. Defining applications lets Heeler roll up findings, scans, and risk at a useful level of abstraction.

### Where to find it

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

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

### Quick start

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

### Reference

#### What an Application captures

* **Name and description** — display fields used throughout the product
* **Repositories** — one or more repos that make up the app
* **Owning team** — the Team responsible
* **Environments** — which Environments this app deploys into (often inferred from observed deployments)
* **Tags / metadata** — for custom categorization

#### Why applications matter

Applications are the level at which Heeler reports security posture to engineering leadership. Findings are still individual, but rolling them up to "Checkout has 3 open critical SCA findings" is what makes posture conversations possible.

### How applications are used

* **Workflows** can branch on application.
* **Dashboards** offer per-application views.
* **Priorities** account for application criticality.


---

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