> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/developer-platform/team-source-platforms.md).

# Team-Source Platforms

Use GitHub, GitLab, or Heeler itself as the source for team and application mapping — no separate integration needed.

Beyond Port.io, Heeler can build **teams and applications** directly from platforms you're already connected to — **GitHub**, **GitLab**, or **Heeler** itself. These aren't separate integrations to add; they're **sources** you pick in Connection Mapping.

## The sources

<table><thead><tr><th width="150">Source</th><th>Teams from…</th><th>Applications from…</th><th>Connection needed</th></tr></thead><tbody><tr><td><strong>GitHub</strong></td><td>GitHub Teams</td><td>Repository <strong>custom properties</strong></td><td>Your existing <a href="/mrecEO40m5D6bt7Pq5pE/get-started/source-code-scm/github.md">GitHub connection</a> — nothing extra.</td></tr><tr><td><strong>GitLab</strong></td><td>GitLab Groups (name or path)</td><td>Path-prefix matching</td><td>Your existing <a href="/mrecEO40m5D6bt7Pq5pE/get-started/source-code-scm/gitlab.md">GitLab connection</a> — nothing extra.</td></tr><tr><td><strong>Heeler</strong></td><td>Manual creation</td><td>Manual creation</td><td>None.</td></tr></tbody></table>

{% hint style="info" %}
Because GitHub and GitLab reuse your [code connection](/mrecEO40m5D6bt7Pq5pE/get-started/source-code-scm.md), there's no OAuth or token to add here — you just choose them as the **Source** in Connection Mapping. Only **Port.io** requires its own [integration](/mrecEO40m5D6bt7Pq5pE/get-started/developer-platform/port-io.md).
{% endhint %}

## Where to configure them

* [**Teams**](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/teams.md) — pick the source, then Configure Mapping (grouping key, allowed values, attribute mapping).
* [**Applications**](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/applications.md) — pick the source; GitHub uses **custom properties**, GitLab uses **path prefixes**.

## Related

* [Map Your Organization → Teams](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/teams.md)
* [Map Your Organization → Applications](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/applications.md)
* [Port.io](/mrecEO40m5D6bt7Pq5pE/get-started/developer-platform/port-io.md) — the full developer-platform integration.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/developer-platform/team-source-platforms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.