> For the complete documentation index, see [llms.txt](https://docs.impossiblecloud.com/partner-portal-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impossiblecloud.com/partner-portal-help/management-console-guide/using-icmc-as-a-distributor/partners/creating-a-partner.md).

# Creating a Partner

To create a new Channel Partner, use the '**Create partner**' button at the top-right of the page. You may now add the partner name and either allocate storage as reserved capacity or create them as 'Pay-per-Use'. To assign the latter, simply leave the 'Allocate storage' field 0.

Storage can be allocated in 1 TB/GB increments using the navigation arrows or could be entered manually, up to your contract's remaining capacity. If additional capacity is required, please contact support.

{% hint style="info" %}
The maximum amount of reserved storage you may allocate is the remaining available capacity of your contract with Impossible Cloud. In case you need more available capacity, simply [reach out](mailto:sales@impossiblecloud.com) our Sales at any time.
{% 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 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.impossiblecloud.com/partner-portal-help/management-console-guide/using-icmc-as-a-distributor/partners/creating-a-partner.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.