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

# Program

## Configuring How Heeler Runs Your Security Program

The **Program** tab is where you configure the policies that drive how Heeler operates day-to-day — the timelines you hold yourself to, the open-source licenses you accept, the remediations Heeler will perform automatically, the template fix PRs use, and the ticket statuses Heeler recognizes as "done."

### Where to find it

Open the **gear icon** in the top-right → **Program** tab.

URL: `https://app.heeler.com/administration/program`

### What's here

| Sub-section              | What it's for                                                                  |
| ------------------------ | ------------------------------------------------------------------------------ |
| Agent PR Template        | The pull-request body template Heeler's agent uses when opening fix PRs.       |
| License Policy           | Open-source license allow/deny rules and approval flow.                        |
| Remediations             | Defaults for how Heeler creates and tracks remediations.                       |
| Service Level Objectives | Remediation timelines per severity / risk bucket, for SCA and SAST.            |
| Ticket Status            | View the status of all tickets Heeler has created — manually or via workflows. |

### Quick start

If you're setting up a new tenant, work through these roughly in this order:

1. **Service Level Objectives** — set your remediation timelines first, since everything else references SLOs.
2. **License Policy** — declare which OSS licenses are allowed.
3. **Remediations** — set Heeler's defaults for remediation behavior.
4. **Agent PR Template** — if you'll use Heeler's agent to open fix PRs, set the template now so all PRs look right.
5. Once workflows are creating tickets, check **Ticket Status** to confirm they're landing where you expect.


---

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