> For the complete documentation index, see [llms.txt](https://legal.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.dispel.com/partner-program/readme.md).

# Dispel Partner Program

At Dispel, our partners are at the heart of how we deliver secure, resilient, and innovative solutions to the world. Our channel is not just a route to market—it’s a community of trusted collaborators who share our commitment to protecting critical infrastructure and advancing cybersecurity.

This section contains the agreements that govern our partner program. They outline the expectations, rights, and responsibilities that ensure fairness, transparency, and mutual success in our partnerships.

Beyond legal terms, we believe strong relationships are built on collaboration and support. That’s why we’ve designed our ways of working to empower our partners—whether through training, joint go-to-market initiatives, or dedicated support resources—so that together we can deliver exceptional outcomes for customers.

{% hint style="info" %}

#### Looking for your Dispel Partner Portal?

<a href="https://partners.dispel.com/" class="button primary">Sign in</a>
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legal.dispel.com/partner-program/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.