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

# Teams

## Defining Engineering Teams

A **Team** in Heeler represents a group of engineers responsible for one or more applications. Teams are the unit of ownership — when Heeler creates a ticket or sends a notification, it routes to a team. Workflows can branch on team. Dashboards roll up by team.

### Where to find it

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

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

### Quick start

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

See the [Getting Started](/getting-started.md) > [Connection Mapping](/getting-started/connection-mapping.md) > [Team Ticket Settings](/getting-started/connection-mapping/team-ticket-settings.md) documentation. 

### Reference

#### Team properties

Each team can have:

* **Name** — display name used throughout the product
* **Owned applications** — set of applications this team is responsible for
* **Members** — user accounts that map to this team 

#### Per-team settings

For each team you can configure:

* **Default messaging tool and channel**
* **Ticketing tool** — which integration to use
* **Project / target** — Jira project key, Linear team, etc.
* **Issue type** — Bug, Task, or whatever your project supports
* **Field defaults** — priority, labels, components, custom fields
* **Routing rules** — what to do when no team is found (default project, default assignee)

#### How Ticketing interacts with Workflows

Workflows reference team ticketing defaults so they don't have to specify ticket destinations explicitly. A workflow can override defaults when needed — for example, a "critical-finding fast lane" workflow might pin all tickets to a security team's project regardless of owning team.

#### Bulk operations

If you have teams to set up, see [Scaling AppSec Operations With Automated Routing and Team Management](/use-cases/scaling-appsec-operations-with-automated-routing-and-team-management.md).

### How teams are used

* **Workflows** route based on team — e.g., "if finding is on a team-owned repo, file a ticket in their default project."
* **Dashboards** can be filtered or grouped by team.
* **Heeler in Slack** uses team channel defaults to know where to post.


---

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