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

# License Policy

## Configuring Open-Source License Approval

The **License Policy** page is where you declare which open-source licenses are acceptable in your code, which require review, and which are outright denied. Heeler uses this policy to flag dependencies whose licenses violate your rules — typically surfaced as License Violations in dashboards and via guardrails.

### Where to find it

Administration → **Program** → **License Policy** in the left sidebar.

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

### Quick start

1. Review the license categories Heeler classifies (Permissive, Weak Copyleft, Strong Copyleft, etc.).
2. For each license or license family, choose its status: **Allowed**, **Requires Approval**, or **Denied**.
3. Configure default behavior for **unknown licenses** — typically *Requires Approval* is the safe default.
4. Save. The policy applies to new and existing findings; existing findings will be re-evaluated.

### Reference

#### Policy levels

Most organizations configure something like:

| Status                | Typical licenses                                             |
| --------------------- | ------------------------------------------------------------ |
| **Allowed**           | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC             |
| **Requires Approval** | MPL-2.0, LGPL variants, EPL, less common permissive licenses |
| **Denied**            | GPL, AGPL, SSPL, commercial-only, no-license                 |

Your exact policy depends on your legal team's view of copyleft, source-disclosure obligations, and SaaS distribution risk.

#### How violations surface

* **License Violations dashboard** — lists current violations and approval status.
* **Guardrails** — can block PRs that introduce dependencies with non-allowed licenses.
* **Workflows** — can route violations to legal or security for review.
* **Agent Skills & CLI** — can guide agents and developers to not introduce dependencies with non-allowed licenses.


---

# 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/license-policy.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.