> 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/administer-and-monitor/connections-and-integrations.md). # Manage Connections and Integrations Every source and tool Heeler connects to, and how to read the Health column so you catch a degraded connection before it costs you findings. Heeler is only as accurate as the sources it can reach. **Administration → Connections** and **Administration → Integrations** are where every connected source and tool lives, each with a **Health** column. You wired these up during [Get Started](/mrecEO40m5D6bt7Pq5pE/get-started.md); this section is about keeping them healthy — spotting a degraded connection, re-authorizing an expired credential, and adding or removing sources as your footprint changes. {% hint style="info" %} Changing anything on this page requires the **Administrator** role. An **Administrator (read-only)** can view it but can't make changes. {% endhint %}

The Connections area under Administration, showing the left rail of connection types and a list of code organizations each with a Health column. — Every connection type has its own sub-tab, and every list carries a Health column.

## In this section


Source Connections	Code organizations, cloud organizations and accounts, Kubernetes clusters, and hosting platforms.	Source Connections
Registries	Package and container registries Heeler reads from.	Registries
Vendor and Trusted Connections	Third parties with access to your cloud — discovered automatically, and the ones you approve.	Vendor and Trusted Connections
On-Premises Brokers	The agents that let Heeler reach private, self-hosted resources.	On-Premises Brokers
Integrations	Ticketing, messaging, and developer-platform tools.	Integrations

## Reading the Health column Every connection and integration reports a **Health** status. Heeler re-checks connections about once an hour (a failed one is re-probed less often, roughly every six hours), so health reflects the last successful check rather than the live instant.

Status	What it means and what to do
✅ Healthy	Authenticated and working. Nothing to do.
⚠️ Degraded	Working, but with reduced permissions — for a GitHub App, some requested permissions haven't been granted yet. Approve the pending permissions to clear it.
⚠️ Impaired Accounts	The organization is healthy, but one or more linked accounts can't be assumed or lack permissions. Open the connection to see which, and fix that account's access.
⚠️ Impaired Visibility	Healthy overall, but specific projects or clusters have disabled APIs or missing permissions, so Heeler can't see everything. Enable the API or grant the permission on the named project.
❌ Error	The connection failed — usually an expired, revoked, or under-scoped credential. Open it and re-authorize or refresh the credential. Analysis for the affected scope pauses until it's fixed.
❌ Inaccessible	The host couldn't be reached at all (network or DNS). Confirm the endpoint is reachable — for private hosts, that a broker is running.
⏳ Created · Ready	Provisioning states you'll mainly see on brokers — the record exists but isn't fully live yet. Give it a moment to finish its first check-in.

{% hint style="info" %} A brand-new connection shows **no health badge at all** until Heeler's first hourly check runs. That's expected — give it up to an hour, then refresh. {% endhint %} When a connection is impaired or failed, the badge's hover card names exactly which accounts, projects, or clusters are affected, so you know precisely what to fix. For whether Heeler is *processing* what it connects to — scan success, errors — see [Operational Health](/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/operational-health.md). ## Related * [Get Started](/mrecEO40m5D6bt7Pq5pE/get-started.md) — first-time setup for every connection type. * [Operational Health](/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/operational-health.md) — scan success and processing status, one level deeper than connection health. --- # 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/administer-and-monitor/connections-and-integrations.md?ask=&goal= ``` `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.