> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/manage-partners/programs-partner-types/how-to-know-when-a-partner-can-move-to-another-program-level.md).

# How to know when a partner can move to another program level?

Make your level requirements measurable, and Kiflo tells you which level each partner qualifies for.

## Prerequisites

* A program with at least two levels. See [How to create a partner program?](/manage-partners/programs-partner-types/create-partner-program.md).
* Only admins can edit level requirements.

## Add a measurable requirement

From **Programs**, open your program, go to the **Levels** tab, select a level, then click **Add requirement** in the **Requirements** section.

Set **Kind** to:

* **Measurable** to let Kiflo track it. Fill in **Name**, **Type**, **Period** and **Target**.
* **Non-measurable** for anything Kiflo cannot see, such as a signed contract. Informational only.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-bd0a6e1761d05e7406798c0cb4648d4909e0e949%2F6a7c6e74d3390e5336e8a29d.png?alt=media)

**Type** offers six options:

* **Number of leads submitted:** The number of leads sourced from the partner
* **Number of deals registered:** The number of deals sourced from the partner
* **Number of deals won:** The number of deals won where the partner is assigned to
* **Revenue generated:** The sum of deals closed won where the partner is assigned to
* **Number of new customers:** The number of new customers sourced from the partner
* **Number of active certifications:** The number of active certifications acquired by the partner's team

**Revenue generated** also asks which deal property to sum, and **Number of active certifications** lets you restrict the certifications that count.

**Period** ranges from **Current quarter** to **All time**, and each requirement has its own. The requirement is met once the partner's value reaches the **Target**.

Click **Add**, then **Save**. Measurable requirements get a **MEASURABLE** tag and a summary such as:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-51b662cf37f597024540f49d236e527047af5214%2F6a7c6f18d3390e5336e8a2a1.png?alt=media)

Requirements created before this feature are kept as non-measurable, so your partner portals are unchanged until you upgrade them.

## How the qualifying level works

The **Qualifying level** is the highest level whose measurable requirements the partner meets, computed per program. It stays empty when it matches the level the partner is already on.

* A level with no measurable requirement is never matched.
* A partner who matches no level qualifies for the program's lowest level.
* Values refresh as partners generate activity, and once a day.
* Kiflo never changes a level on its own.

## See who qualifies

The **Qualifying level** appears in three places, and always stays empty for partners who are already on the right level.

**Members tab of your program.** The **Qualifying level** column sits next to **Level**, so you can scan a whole program at once and spot the rows where the two differ. Each value links to the level it points to.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-ab491a250c16999817d4e6612489f6089cb50e02%2F6a7c6f83d3390e5336e8a2a4.png?alt=media)

**Partners page.** The same column covers every program at once. Partners in a single program show just the level name, and partners in several show one `[program] - [level]` pair per program. If you do not see the column, click **edit columns** above the table and add **Qualifying level**. To work through a list of candidates, click **Show filters** and filter on **Qualifying level**.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-150afa98a85ddce499b0066b9799eeac4cc1ce33%2F6a7c6fd8d3390e5336e8a2a9.png?alt=media)

**Partner page.** Each program section shows the partner's **Qualifying level** next to their assigned level, and a warning explains which way they are drifting:

* a promotion, when they meet all the requirements of a higher level,
* a demotion, when they no longer meet the requirements of their current level and qualify for a lower one.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-57d10bc0a4c44376e2b9dc03e184a5f59ff0b37a%2F6a7c700c714de94e758bab44.png?alt=media)

## Move partners to their qualifying level

Reassigning a level is always your call, and you can do it from the same three places. You need the permission to edit partners to see the action.

**One partner at a time.** On the partner page, click **Move to qualifying level** in the warning of the program concerned, then confirm. Only that program's level changes, so a partner enrolled in several programs keeps their other levels.

**A batch of partners.** On the **Partners** page, tick the partners you want to move, click **MOVE TO QUALIFYING LEVEL** in the toolbar, then confirm. The same action is available on the **Members** tab of a program, where it only touches the levels of that program.

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-aa8f80a162323169c2b70e1034fc1efa6fb277ff%2F6a7c7061bdad84857311a5e2.png?alt=media)

Good to know:

* The action moves partners in both directions, promotions and demotions alike.
* Partners already at their qualifying level are left unchanged, so you can safely select a whole page.
* Kiflo confirms how many partners were moved, and their **Qualifying level** clears once it matches their new level.


---

# 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-vnext.kiflo.com/manage-partners/programs-partner-types/how-to-know-when-a-partner-can-move-to-another-program-level.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.