Partner & reseller portal

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

What is a partner & reseller portal?

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. It follows the Client hubs pattern: one shared space per client: deliverables, documents, milestones. Pory generates it from a plain-English description, with a login for each role (partner and channel manager) that shows only what that role should see, and flat pricing with unlimited partners.

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, an estimated value 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 battlecard, deck, case study and logo pack is a card in the asset library, labelled 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

The parts every portal is built from

Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.

Collect

Forms

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

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

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

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Record pop-up & linked records

A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the rows a viewer is allowed to read.

Control

Role & row access

Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.

No-Password Doors

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

Your brand

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

On purpose

Four things Pory won’t do

A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.

Take payments

Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.

Book time slots

Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.

Host the conversation

No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.

Plan routes

Pory keeps the service record, not the map.

Frequently asked questions

Your partner & reseller portal, live today.

Describe it in a sentence and send the invite. Unlimited partners, flat price.