> For the complete documentation index, see [llms.txt](https://docs.zeedrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeedrive.com/partner-guide/request-a-partner-subscription.md).

# Request A Partner Subscription

If your organisation doesn't already have a <code class="expression">space.vars.PRODUCT\_NAME</code> Partner Subscription but you would like one, then first download and review the [Partner Subscription Agreement](/resources/terms-and-conditions.md), and if you are in agreement, then [contact support](/resources/contact-support.md) and we'll get you set up with a new Partner Subscription.

The Partner Subscription is free.

Customer subscriptions that you may already be administering can be transferred to your new Partner Subscription.

A Partner Subscription starts with 3 Partner User Licences (so you and up to 2 other colleagues can use the Partner Subscription) and an initial maximum of 20 customer subscriptions can be administered.

These limits can be increased on request should your usage of the <code class="expression">space.vars.PRODUCT\_NAME</code> Partner Subscription grow.


---

# 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://docs.zeedrive.com/partner-guide/request-a-partner-subscription.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.