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

# Administer and Monitor

Run Heeler day to day: manage who has access, keep your connections and integrations healthy, set the policies the loop follows, and confirm the platform is operating correctly.

Everything under the **gear icon → Administration** lives here. You did the first-time setup in [Get Started](/mrecEO40m5D6bt7Pq5pE/get-started.md) — connecting your code and cloud, inviting your team, mapping your organization. This section is about **running Heeler afterward**: managing what's already connected, controlling who can do what, tuning the rules the platform follows, and confirming it's all working.

You need the **Administrator** role to change anything in this section. An **Administrator (read-only)** can see it but not modify it.

## Administer

Manage and change what you set up during onboarding.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Manage Access</strong></td><td>Who can use Heeler, how they sign in, and the keys that talk to the API.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/manage-access.md">Manage Access</a></td></tr><tr><td><strong>Connections &#x26; Integrations</strong></td><td>Every source and tool Heeler talks to — and whether each one is healthy.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/connections-and-integrations.md">Manage Connections and Integrations</a></td></tr><tr><td><strong>Organization Model</strong></td><td>Keep your teams, applications, environments, and ticket routing accurate as the org changes.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/organization-model.md">Maintain the Organization Model</a></td></tr><tr><td><strong>Program Policy</strong></td><td>The tenant-wide rules the loop follows — the agent, licenses, routing, SLOs, and more.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/program-policy.md">Set Program Policy</a></td></tr></tbody></table>

## Monitor

Confirm Heeler is doing its job — and see who changed what.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Operational Health</strong></td><td>Is Heeler scanning and guarding cleanly — success rates, errors, guardrail timing.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/operational-health.md">Operational Health</a></td></tr><tr><td><strong>Agent Executions</strong></td><td>The audit trail of every remediation-agent run — plan, tool calls, PR, status. Lives under <strong>Fix</strong>.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/fix/agent-executions.md">Agent Executions</a></td></tr><tr><td><strong>Audit Log</strong></td><td>Every change made in Heeler — who, what, when, and from where.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/audit-log.md">Audit Log</a></td></tr></tbody></table>

## Where setup lives instead

To connect or configure something for the **first time**, start in Get Started — this section assumes it already exists and focuses on managing it:

* [Connect Your Code](/mrecEO40m5D6bt7Pq5pE/get-started/source-code-scm.md) · [Cloud & Runtime](/mrecEO40m5D6bt7Pq5pE/get-started/cloud-and-runtime.md) · [Registries & Artifacts](/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts.md)
* [Connect Ticketing](/mrecEO40m5D6bt7Pq5pE/get-started/ticketing.md) · [Messaging](/mrecEO40m5D6bt7Pq5pE/get-started/messaging.md) · [Developer Platforms](/mrecEO40m5D6bt7Pq5pE/get-started/developer-platform.md)
* [Users and Access](/mrecEO40m5D6bt7Pq5pE/get-started/users-and-access.md) · [Map Your Organization](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization.md)


---

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