Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.partneros.ai/llms.txt

Use this file to discover all available pages before exploring further.

Your partner program configuration in PartnerOS defines how partners are classified, what requirements they must meet to reach each tier, and how those tiers map to your broader go-to-market motion. The program is built from three layered concepts: segments, tracks, and tiers. Getting this structure right means the Partners table, intelligence dashboards, and executive reports all reflect the way your organization actually thinks about its partner ecosystem.
The Partner Program page is only accessible to org admins. Go to Partner Program in the sidebar to manage your program configuration.

​
Core concepts

​
Segments

Segments are the broadest groupings in your program. They represent distinct markets or motions — for example, a segment for solution partners, one for technology alliances, and one for sales partners. Each segment belongs to one of three families:
FamilyWhat it represents
marketPartner groups defined by the market they serve or the buyer they reach
technologyPartners who build integrations or complementary products
servicesPartners who deliver implementation, consulting, or managed services
Each segment has a name, a definition that describes what qualifies a partner for it, and requirement logic — a set of configurable rules that determine eligibility. Requirement rules can check fields like deal volume, employee count, certifications, geography, or tags using operators such as gte, lte, between, includesAny, includesAll, and equals. PartnerOS ships with a set of seed segments based on common go-to-market patterns. You can use these as a starting point and customize them to fit your program.

​
Tracks

Tracks sit inside segments and group the tiers for that segment. In the PartnerOS interface, tracks are displayed as segments — the database uses the term track internally to distinguish them from the broader market-segment concept above. Each track has:
  • Name — a label shown in the UI and reports
  • Slug — a URL-safe identifier generated from the name
  • Description — optional context for admins managing the program
  • Sort order — controls the display order in the program page
Tracks let you run multiple tier ladders side by side. For example, you might have a “Reseller” track with Gold, Silver, and Bronze tiers, and a separate “Technology Alliance” track with its own tier structure.

​
Tiers

Tiers are the levels within a track that partners progress through. Common tiers include Platinum, Gold, Silver, Bronze, and Registered, but you can create custom tiers with any name and color. Each tier has:
  • Name — displayed on partner profiles, the Partners table, and reports
  • Color — a visual indicator (amber, blue, purple, green, orange, red, slate, or neutral)
  • Sort order — the rank within the track, used to determine progression
  • Requirement logic — the rules a partner must satisfy to qualify for this tier
Tier assignment in PartnerOS works in two modes:

Auto-evaluated

PartnerOS evaluates each partner against the requirement logic you configure and assigns the highest tier they qualify for. The evaluation runs automatically and records a timestamp so you can see when it last ran.

Manual override

You can manually assign any tier to a partner from their profile. A manual assignment records the tier source as manual and is not overwritten by automated evaluation until you clear the override.

​
Configuring your partner program

1

Open the Partner Program page

Navigate to Partner Program in the sidebar. You must be an org admin to access this page. The page loads your current tracks, tiers, and segments.
2

Set up or review segments

Review the existing segments (or seed the defaults if none exist yet). Edit segment names, definitions, and requirement logic to match your program’s eligibility criteria. Each segment’s requirement logic specifies the fields that matter — for example, requiring a minimum deal count, specific certifications, or a particular region.
3

Configure tracks

Add tracks to represent the distinct partner groups in your program. Use the Seed default tracks action if you want to start from PartnerOS’s standard structure and then customize. Each track you create appears as a column or grouping in the Partners table tier selector.
4

Define tiers within each track

For each track, create the tiers that make up the ladder. Set the name, color, sort order, and requirement logic for each tier. The sort order determines which tier is considered higher — assign lower sort order numbers to higher-prestige tiers.
5

Assign partners to tiers

Once tracks and tiers are configured, partner tier assignment updates automatically based on requirement logic. You can also assign tiers manually from any partner profile.

​
Requirement logic

Requirement logic is the set of rules that determine whether a partner qualifies for a given segment or tier. Each rule targets a specific field and uses an operator to define the condition.
Use between, gte (greater than or equal), or lte (less than or equal) to set numeric thresholds. For example, you might require a partner to have at least 10 closed deals, or a company revenue between 1Mand1M and 50M. Set a min and/or max value, or use a single boundary with gte or lte.
Use equals to match a single string value, such as requiring a specific industry classification or region.
Use includesAny or includesAll to match against a list of values. includesAny passes if the partner matches at least one value in the list. includesAll passes only if the partner matches every value. These are useful for tag-based rules — for example, requiring a partner to have both a “certified” and a “managed-services” tag.
Each rule supports an optional notes field. Use it to document the intent behind the rule or any exceptions your team should be aware of. Notes are visible only to admins in the program configuration view.
Start with a small number of meaningful rules per tier. Overly complex requirement logic can make it hard to explain tier criteria to partners and difficult to maintain as your program evolves. Add rules incrementally as you validate what actually distinguishes your best partners.

​
How program structure connects to the rest of PartnerOS

Your program configuration flows through the product in several places:
  • Partners table — the type-to-tier cascade in the Partners table is driven by your segment and track configuration. Selecting a partner type shows the tiers available for that type.
  • Intelligence dashboards — the Executive Dashboard lets you filter metrics by segment and tier, using the same definitions you configure here.
  • Executive updates — when generating executive summaries and quarterly reviews, you can filter by segment to scope the report to a specific part of your program.
  • Strategy workspace — top-matching partner recommendations in the strategy workspace take your program structure into account when surfacing partner candidates.