Partner & reseller portal with deal registration

A partner and reseller portal is where partners register deals and pick up sales assets, the channel team approves or rejects each registration with a reason, and each partner sees only its own deals.

Pattern: Client hubs

Describe it to Pory

“We sell endpoint security through IT resellers. Partners register deals so we can protect them, our channel manager approves registrations, and partners get a library of sales assets.”

Viewing as

My deals

My deals

Powered by Pory

In plain English

How Pory sets it up

Pory gives every partner and channel manager a sign-in of their own. Each partner sees only their own deals. It covers deal registration & assets. Deals, asset library, training and bastion team live in Pory's own database, so there's no spreadsheet to keep in sync.

What it does

01

Resellers register a deal before a rival reseller does

Deal registration used to be an email to the channel manager, and two partners chasing the same account found out at the proposal stage. In Pory a partner enters the opportunity, the end customer, the product, the seat count and an expected close date, and the registration lands as Submitted under their name. The channel manager stops refereeing reply-all disputes.

Forms to submit a recordDone by: Partner
02

The channel manager approves or rejects registrations with the reason recorded

Approving a registration used to mean checking a spreadsheet for conflicts and then remembering to email back. The channel manager opens a registration, checks it against other deals for the same end customer, and approves or rejects it, writing the reason on the deal. A rejected partner learns why from the record, not a phone call.

Approve / reject with a reasonDone by: Channel manager
03

Partners pick up battlecards and pitch decks from one asset library

Partners used to ask for "the latest deck" and receive whichever file the channel manager found first. In Pory each datasheet, battlecard, pitch deck, case study and demo video is a card in the asset library, labeled by type and product. Partners take what they need themselves, and nobody pitches with last year's slides.

Gallery & image gridDone by: Partner
04

Each reseller sees its own registrations and never a competitor's

A shared deal sheet was never an option, because partners compete with each other for the same accounts. In Pory each partner signs in to their own view: the deals they've registered, where each stands and when it's expected to close. The channel manager sees every partner's deals on one list, and no partner sees another's.

Client-only accessDone by: Partner

Who sees what in a partner & reseller portal

Every person signs in to their own view. This is what each role in the demo gets.

Partner

Sees only their own deals.

Pages
Home, My deals, Asset library, Training, Rules of engagement
Can start
Register a deal, New deal

Channel manager

Sees every deal in the portal.

Pages
Home, Deals, Expected closes, Asset library, Partner training
Decides
Marks deals Approved or Rejected, with a reason

What’s in the partner & reseller portal template

The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.

Deals

  • Opportunity (text)
  • End customer (text)
  • Partner rep (link)
  • Product (choice: Bastion Mail, Bastion Endpoint, Bastion Mail + Endpoint)
  • Seats (number)
  • Expected close (date)
  • Estimated value ($) (number)
  • Protected until (date)
  • Status (choice: Submitted, Under review, Approved, Closed won, Rejected)
  • Notes (long text)

Asset library

  • Asset (text)
  • Type (choice: Datasheet, Battlecard, Pitch deck, Case study, Demo video)
  • Product (choice: Bastion Mail, Bastion Endpoint, Bastion Mail + Endpoint)
  • File (file)
  • Added (date)

Training

  • Course (text)
  • Partner rep (link)
  • Status (choice: Not started, In progress, Passed)
  • Due (date)

Bastion team

  • Name (text)
  • Role (text)
  • Region (text)

The parts behind this portal

Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal

Collect

1 part
  • Forms

    Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Decide

1 part
  • Approve / reject with a reason

    Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Share

1 part
  • Gallery & image grid

    Records as cards or photos.

Control

3 parts
  • Who sees which records

    Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.

  • Passwordless sign-in

    A sign-in link by email, by default. Password sign-in if you'd rather.

  • Your brand

    Your domain, your colors, your logo. Members see you.

Frequently asked questions

A partner signs in with a link sent to their email and lands on Home. They see Home, My deals, Asset library, Training and Rules of engagement, and only the deals that are theirs. From there they can use “Register a deal” and “New deal”.

Channel manager decide: they mark each one Approved or Rejected and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.

You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.

Build your partner & reseller portal with Pory

Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited partners.

See pricing · How Pory builds a portal