My deals
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 hubsDescribe 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.”
My deals
In plain English
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
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.
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.
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.
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.
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
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
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.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
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.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited partners, flat price.