---
title: "Partners"
id: "2147"
type: "page"
slug: "partners"
published_at: "2026-10-04T08:29:33+00:00"
modified_at: "2026-10-22T16:38:23+00:00"
url: "https://xedant.com/agents/crm/addons/partners/"
markdown_url: "https://xedant.com/agents/crm/addons/partners.md"
excerpt: "The add-on Partners gives your resellers, dealers and agencies a cabinet on the portal: they…"
---

# Partners

[https://xedant.com/agents/crm/addons/partners/.md](https://xedant.com/agents/crm/addons/partners/.md)

The add-on **Partners** gives your resellers, dealers and agencies a cabinet on the portal: they register the customers they are working on — and the first registration holds the claim — receive the leads you assign to them, and download the price lists you decided to share.

![Partners add-on: the partner accounts with tier, kind, status, certification and channel manager](https://xedant.com/wp-content/uploads/2026/10/crm-agent-addon-partners.png)## Why you need it

Partner work usually rests on email threads and phone calls. Who brought the customer first is an argument in which each side has its own memory. A partner does not know which leads were handed over or until what date their customer is protected. Price lists are mailed out by hand, and there is always one partner quoting last year’s. Internal and partner sales are counted in different files, so it is impossible to see who actually brings the money.

Partners turns those agreements into records. A claim is submitted from the cabinet, the decision and its reason are visible to both sides, the protection has an exact end date, leads and price lists are handed over in one place and according to the partner’s tier, and an approved claim becomes an ordinary deal in your own pipeline — plainly marked as brought by a partner.

## What it does

- **Partner accounts.** Each partner has a card: name, programme, tier (silver, gold or platinum), certification, region and a channel manager — the person on your side who runs the partner and is notified about their claims. One account carries at most 500 registrations, 25 linked users, 200 lead grants and 200 shared files.
- **Sign-in through the portal.** A partner is a portal user, so passwords, invitations and permissions live in [Portal](/agents/crm/addons/portal) rather than in a separate list; one portal user belongs to exactly one partner account, and the partner scope word gates the cabinet door. There is no second login to maintain.
- **Deal registration.** The partner submits the end customer they are working on. The claim key is the company’s name reduced to one normalised form, so “Acme Ltd” and “acme ltd” are one claim and not two — a second attempt under a different spelling cannot slip through. A registration moves through submitted and in review, and then to approved, rejected or expired.
- **The conflict rule.** What happens when two partners claim the same customer is a setting, chosen once and stored in the channel rules. “First registered” refuses the later claim and names its evidence; “house pipeline” queues partner-versus-partner disputes for your office; “strategic partner” lets a gold or platinum submitter queue past a strictly lower tier. Under every rule, your own open deal outranks any tier.
- **The protection window and the verdict.** Protection lasts 90 days by default and can be set anywhere from 7 to 365 days. Every verdict — clean, queued or refused — is journaled with the rule word and the evidence rows, refused submissions included. A rejection’s reason is mandatory: the partner reads it verbatim in the cabinet, so “declined for internal reasons” is not a sentence you can write here.
- **Approval births an attributed deal.** An approved registration creates a real deal in your pipeline with the partner provenance on it: the source is marked as a partner, and the partner’s name and the registration’s id travel with the deal, so reports can be cut by partner and by tier immediately. The deal is seated once — a decided registration never re-decides, so duplicates cannot appear. If the company name matches more than one record, the approval refuses by name instead of guessing the customer.
- **Window expiry.** Once a day the product checks the standing windows. A lapsed registration moves to expired exactly once, journaled and lettered to the partner’s users, and the customer becomes free for another partner. Replaying the pass changes nothing and never twins the row.
- **Assigned leads.** Your office hands specific leads to a partner. There are two modes: an immediate assignment, or an offer the partner accepts themselves — and the acceptance is journaled as their commitment. One lead is held by one partner at a time, so a second standing hand refuses by name; the office can pull a hand back, the revocation stays in history while the lead becomes free again; and the partner’s linked users receive a letter about every change.
- **Price lists and materials.** Each shared file is addressed either to one named partner or to everyone at or above a given tier. Rank is judged at download time, not at upload time, so nobody works from a price list they are no longer entitled to. The cabinet carries a price-list shelf showing exactly what is open to that partner.
- **The partner’s cabinet.** Three things, no more: their registrations with verdicts and window ends, the queue of handed and offered leads (accepting an offer is a single action), and the price-list shelf. A partner sees neither your internal notes nor other partners’ deals.
- **The partners console on your side.** One section with the tabs Registrations, Partners, Leads and Pipeline: “The registration board” with standing claims and windows about to end, “The partner accounts”, “The lead queue — hands, not a firehose”, “The partner pipeline — attributed on read”, “The tier cuts” and “Volume by partner”. The “Channel desk” panel on the home screen shows the claims waiting for your decision and the windows on the edge of expiry. Every total is computed at the moment you look, never stored as a stale snapshot.
- **Emails and the account lifecycle.** Letters go out over the system mail path on the decision, expiry and grant moments. A partner account with history cannot be deleted — the product refuses and names the linked users, registrations, grants and shares that stand in the way — but it can be suspended, which stops the contour’s writes by name while the history stays.

## How it relates to other add-ons

Partners declares two required add-ons — **portal** and **deals** — and will not install without them. [Portal](/agents/crm/addons/portal)
 provides the cabinet and the sign-in: a partner is a portal user, so passwords, invitations and rights live there rather than in a separate list, and the partner scope word gates the door. [Deals](/agents/crm/addons/deals)
 provides the pipeline: an approved claim becomes an ordinary deal in it, and the conflict check reads your team’s own open deals. The order is therefore Deals and Portal first, then Partners — and the product will not let you switch either of them off while Partners runs, naming which one is in the way, because the partners would have nowhere to sign in and an approved claim would have nothing to turn into. Beyond those two, partner deals simply live on in the shared pipeline with everyone else’s, so the deals reports you already read include them.

## Honest limits

- Commissions, shared marketing budgets, partner learning and a partner offer marketplace are not in this add-on. The seats for them exist, but accrual and payout are not built, so count partner rewards outside the product for now.
- A partner’s tier is set by hand: there is no automatic promotion by sales volume and no automatic demotion. The tier is your decision, not a computed figure.
- The office always outranks the partner: an open deal of your own team beats any partner claim under every conflict rule, whatever the tier or the money involved.
- A registration is decided once and a window expires once. Protection cannot be extended retroactively and a rejected claim cannot be re-decided — otherwise the history would stop being evidence. A new attempt is a new registration.
- A partner cannot cancel their own accepted lead: only the office revokes a grant. That is deliberate — accepting a lead is the partner’s commitment to you.
- One lead is held by one partner at a time; one partner account belongs to one portal user; and a single partner carries at most 25 linked users, 500 registrations, 200 lead grants and 200 shared files.
- An account with history cannot be deleted — suspend it instead. And when a company name is ambiguous, the product refuses by name rather than guessing the customer: the office decides that by hand.
- The partner cabinet is plain server pages: no separate mobile apps, some internal labels remain in English, and there are no phone notifications — only letters on the decision, expiry and grant moments. The partners console itself only reads, and changes are made by agent commands, copyable in one click; that is a deliberate product-wide rule that the interface does not write. A partner’s tier also does not automatically unlock catalogue items — such an item answers “ask the office” until the tier machinery is in place.

All add-ons → [Add-ons catalogue](/agents/crm/addons)

[← CRM Agent documentation](/agents/crm/docs)