> 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/connections/code-organizations.md).

# Code Organizations

A **Code Organization** is a connection to a source-code host (GitHub, GitLab, Bitbucket, Azure DevOps). Heeler uses these connections to discover repositories, perform SAST and SCA scans, post pull-request feedback, and (with agentic remediation) open fix PRs.

### Where to find it

Administration → **Connections** → **Code Organizations** in the left sidebar.

URL: `https://app.heeler.com/administration/connections/scm_accounts`

### Quick start

[See Code Setup documentation](/getting-started/code-setup.md).

### Reference

#### Table columns

| Column         | Description                                                   |
| -------------- | ------------------------------------------------------------- |
| **Name**       | The organization name as reported by the provider.            |
| **Health**     | Connection status. Healthy = actively connected and scanning. |
| **Date Added** | When the connection was first created.                        |

#### Actions

* **Add Code Organization** — start a new connection flow.
* Clicking an existing row opens its detail view, where you can see scanned repositories, rotate credentials, or disconnect.

#### Health states

* **Healthy** — Heeler is reaching the provider and scans are succeeding.
* **Degraded** — credentials are expiring or some scans are failing. Investigate via Operational Health.
* **Broken** — Heeler can no longer authenticate. Re-run the install flow.

### Related documentation

* Code Setup — provider-specific install guides
* Bitbucket Cloud
* GitHub Enterprise Server
* On-Premises Broker — for SCM hosts behind a firewall


---

# 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/connections/code-organizations.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.