> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/get-started/getting-started-agencies/get-started-as-an-agency/how-to-use-a-partner-code.md).

# How to use a Partner code

Learn what a Partner code is, how partner levels work, and where to add the code.

{% hint style="info" %}
For the full Agency Partner Program overview, start with [Get started as an agency](/get-started/getting-started-agencies/get-started-as-an-agency.md).
{% endhint %}

<details>

<summary>What is a Partner code?</summary>

This code is linked to a specific marketing agency and is used to determine which accounts are actively managed by the linked agency.

The Partner code is shared by Channable when the partner agreement is signed.

</details>

<details>

<summary>How is my Partner Level determined?</summary>

Your partner level is based on your managed customers and their combined revenue.

For the full overview of partner levels, benefits, and training criteria, see [Get started as an agency](/get-started/getting-started-agencies/get-started-as-an-agency.md).

</details>

### Fill in Partner code

To add a Partner code to a Channable account, **the agency first has to be** [**granted access** **to the account**](/get-started/getting-started-agencies/agency-dashboard/request-access-to-existing-companies.md)**.**

Once the agency has access to the account, the company owner can add the code.

{% hint style="warning" %}
Only users with the **Owner** role can fill in the Partner code as the managing agency. Learn more about [user roles and rights](/account-billing/manage-your-account-and-settings/manage-user-roles-in-a-channable-account.md).
{% endhint %}

1. Open **Company settings**:

{% tabs %}
{% tab title="Modern version" %}
While in a company, click **Company settings** in the sidebar, or select the **\[your company]** dropdown and click **Company settings**.
{% endtab %}

{% tab title="Legacy version" %}
While in a company, click **Company settings** in the sidebar.
{% endtab %}
{% endtabs %}

2. Select **Agency details**.
3. At **Managing agency (partner code)**, enter the Partner code in the text field.
4. Click **Save**.

{% hint style="warning" %}
If your Partner code isn't filled in, you **won't** receive Partner commission from Channable for managing those clients.&#x20;
{% endhint %}

### How to check if you're receiving partner commission for a client

1. In your **Agency Dashboard**, check the **Managing agency** column.

If you see a <i class="fa-circle-check">:circle-check:</i> check icon, you've added a partner code to that account and are eligible for partner commissions.


---

# 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://helpcenter.channable.com/get-started/getting-started-agencies/get-started-as-an-agency/how-to-use-a-partner-code.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.