Connection Mapping

Heeler's Connection Mapping lets you define how your external platforms — source control, software catalogs, and cloud providers — translate into Heeler's organizational model. Instead of manually creating teams, applications, and environments, you configure the mapping once and Heeler keeps everything in sync automatically.

What Is Connection Mapping?

Connection Mapping bridges the gap between your existing tools and Heeler's security platform. Your organization already defines team structures in GitHub, application groupings in Port.io, and environment boundaries in AWS, Azure, and GCP. Connection Mapping reads these definitions and mirrors them in Heeler — so your security posture reflects the same organizational reality your engineers work with every day.

How It Works

1. Connect your platforms under Administration > Connections (GitHub, GitLab, Port.io, AWS, Azure, GCP)

2. Configure mappings under Administration > Connection Mapping to define how external entities map to Heeler concepts

3. Heeler syncs automatically — teams, applications, and environments stay up to date as your organization evolves

What You Can Map

Mapping	What It Does	Sources
Team Mapping	Organizes repositories by team ownership based on your existing team structures	GitHub Teams, GitLab Groups, Port.io Teams
Application Mapping	Groups repositories into applications for aggregated security visibility	GitHub Custom Properties, GitLab Path Prefixes, Port.io Blueprints
Environment Boundaries	Maps cloud accounts, subscriptions, and clusters to deployment environments (Production, Staging, Development)	AWS, Azure, GCP, Kubernetes

Why Configure Connection Mapping?

• Automated onboarding: New repositories, services, and cloud resources are automatically assigned to the correct team, application, and environment

• Accurate security context: Findings, vulnerabilities, and secrets are attributed to the right owners with the right business impact

• Reduced manual effort: No spreadsheets, no tickets to engineering — admins configure mappings through the UI and Heeler does the rest

• Organizational consistency: Heeler reflects the same structure your teams already use, not a separate taxonomy to maintain

Getting Started

Navigate to Administration > Connection Mapping to access the configuration for each mapping type. The sidebar provides quick access to:

• Teams — Configure team source and attribute mapping

• Applications — Configure application source and attribute mapping

• Environments — Assign cloud accounts and clusters to environment boundaries

• Ticketing — Configure default ticketing integration settings

Connection Mapping requires at least one active connection configured under Administration > Connections. The available mapping sources are filtered to only show platforms you've already connected.