Partner management for security vendors

Where the program is decided

One registration, several claimants
A large deal arrives with an MSSP, a reseller, and whoever brought the customer. The registration names them, so credit is argued from the record.
Partner groups decide who sees which pricebook
Membership rules re-evaluate on a schedule, so access follows a partner's real status rather than a manager's memory.
Sourced and influenced revenue, side by side
Read by partner and by tier, in the same place the deals were registered.

Register

The claim arrives with its own evidence

A registration carries the account, the partner that filed it, the co-seller and the distributor, so the question of whose deal it is has an answer before anyone has to remember one.

Protect

Rules of engagement, written once

Approval and status sit on the registration, and the partner can read the state of its own claim without asking a channel manager to go and check.

Credit

Two partners, one opportunity

Complex security deals involve an MSSP running the service and a reseller holding the paper. Both are named on the record, so credit is argued from it rather than from a first-to-file rule.

Each partner type opens the portal for a different reason

: Runs your product inside a service it operates for the customer, so your license never appears in the buyer's decision. What it asks you for is escalation paths, release notes, and certifications its own engineers can hold.
: Buys at a discount and sells on with its own configuration and services attached. Margin is the whole relationship, which is why registration is where the trust is won or lost.
: Stands between you and the resellers, carries the credit risk, and often runs the enablement you would otherwise run yourself. You see its sell-in; the sell-through is something you have to ask for.
: Builds your product into a project long enough that it may never transact with you at all. Its influence turns up as revenue that no invoice from it will ever explain.
: Sells its own product with yours attached, and the joint customer belongs to both companies at once. Attribution is the awkward part, and it wants settling before the first shared deal.

Ask who registered the deal first

A registration names every partner that claimed the account, so the assistant your team already has open can say who filed first and which of them is certified to close it.

Sign-in happens in your browser, so there is no token to issue or rotate, and the assistant reaches only the data your own account already reaches.

See Agent Connect

ChatGPT
Claude
Gemini
Copilot

Registration is where a security channel wins or loses trust

Can two partners register the same deal?

Yes, and on a large security deal that is usually the honest description of what happened. A registration can name the co-seller and the distributor alongside the partner who filed it, so the record matches how the deal was sold rather than who reached the form first. Multi-partner deal registration.

How do we keep the direct team out of a registered deal?

By writing the rule once and letting the registration carry it. Approval and status sit on the registration itself, so a partner can see the state of its own claim without asking a channel manager to go and check. Rules of engagement.

What does an MSSP need from the portal that a reseller does not?

It needs less pricing and more roadmap. A reseller opens the portal to quote and to register, whereas an MSSP has already absorbed your product into a service it operates, so what it comes for is escalation paths, release notes and the certifications its engineers have to hold. Managed security service provider.

Do partners need a login to our CRM?

No. Partners work in their own portal, and the deal, lead and status records sync to whatever your revenue team already runs, so nobody outside the company is issued a seat in your CRM in order to file a registration.

Can one portal serve resellers and alliance partners at once?

One portal is the normal arrangement, and partner groups are the mechanism. A group decides which content, pricebooks and courses a partner reaches, and membership is re-evaluated on a schedule rather than maintained by hand, so an alliance partner never opens the reseller's price list. Technology alliance.

Security and access control

You are giving hundreds of outside companies a login. The controls matter more than in most software you buy.

: Configured separately for the partner portal and the admin console, each with its own client and fallback handling.
: Auth0, on your own tenant. You supply the application and hold the keys.
: Scoped by partner group. Membership rules re-evaluate on a schedule and again when a partner signs in.
: Assigned per user rather than per partner account, so seniority inside a partner matters.
: Impersonation opens a partner's exact portal view, so a reported issue is reproduced rather than described.

Register one deal for two partners during the demo

Get a demo

Your reseller has other vendors