> ## Documentation Index
> Fetch the complete documentation index at: https://docs-vnext.kiflo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner Programs in Kiflo: Overview and Key Concepts

> Learn what partner programs are in Kiflo, how they differ from partner types, and what you can configure per program to power your ecosystem.

Partner programs are the top-level structure you use to segment and manage the partners in your ecosystem. Each program groups partners who operate in the same way — for example, all referral partners in one program and all resellers in another — giving you a clear, organised view of every relationship and making it easy to tailor benefits, rewards, and portal experiences for each group.

## Why programs matter

When you run multiple go-to-market motions, treating every partner identically creates noise. Programs let you define distinct rules for each motion so that a referral partner sees a referral-specific portal, earns referral-specific rewards, and signs program-specific terms — without any confusion spilling over from your reseller program.

## Tiers and levels within a program

Inside a single program you can create multiple tiers — commonly called Bronze, Silver, and Gold — each with its own:

* **Requirements** — the performance thresholds a partner must hit to qualify
* **Benefits** — the perks or resources unlocked at that level
* **Rewards** — the commission rates or bonuses attached to the tier

This lets a single "Referral Program" scale from a basic entry tier all the way up to a high-commitment elite tier, without needing separate programs.

## Partner Types vs. partner programs

Programs and partner types are complementary, but they solve different problems.

| Concept             | What it does                                                                                                                       |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Partner Program** | Groups partners by their go-to-market motion (referral, reseller, affiliate) and defines tiers with different benefits and rewards |
| **Partner Type**    | Adds a finer label within a program — for example, *Agency*, *Consultant*, or *System Integrator* inside a Referral Program        |

<Note>
  If you don't need to distinguish the specific type of partner within a program, you can safely ignore partner types. They're entirely optional.
</Note>

## What you can configure per program

Every program has its own set of settings you can customise independently:

* **Automated emails** — send acknowledgement emails when a partner applies, is accepted, or is rejected
* **Terms & Conditions** — link your T\&Cs so partners must accept them before accessing the portal for the first time
* **Portal feature flags** — control whether partners in this program can submit leads, register deals, update deals, or change deal stages
* **Application form** — connect an external sign-up form so prospects can apply directly to this program
* **Partner types** — attach one or more partner types to partners in this program for extra granularity

<Tip>
  You access all of these settings by going to **Programs**, selecting a program, and clicking the **Settings** tab.
</Tip>

## Next steps

<CardGroup cols={2}>
  <Card title="Create a Program" icon="plus" href="/programs/create-program">
    Follow the step-by-step guide to create your first partner program and customise its settings.
  </Card>

  <Card title="Partner Types" icon="tags" href="/programs/partner-types">
    Learn how partner types differ from programs and how to add, rename, or reorder them.
  </Card>

  <Card title="Invite Partners" icon="user-plus" href="/partners/invite-partners">
    Add partners to a program manually or let them apply through a sign-up form.
  </Card>

  <Card title="Partner Prospection" icon="binoculars" href="/partners/partner-prospection">
    Track potential partners through a pipeline before they become active.
  </Card>
</CardGroup>
