An affiliate program portal is where creators sign up as affiliates, the partnerships team approves or rejects each one with a reason, and approved affiliates track their own commission payouts month by month.
Pattern: TrackingDescribe it to Pory
“We sell hiking gear online. Bloggers and YouTubers sign up to our affiliate program, we approve the good fits, and each affiliate sees their own monthly payouts.”
Join Trailhead Affiliates
Create your account as a affiliate. We'll email you a link to finish.
In plain English
An affiliate program portal is where creators sign up as affiliates, the partnerships team approves or rejects each one with a reason, and approved affiliates track their own commission payouts month by month. It follows the Tracking pattern: a person's or asset's history, built up over time. Pory generates it from a plain-English description, with a login for each role (affiliate and partnerships manager) that shows only what that role should see, and flat pricing with unlimited affiliates.
What it does
Affiliate applications used to come through a contact form, and someone created each account by hand once they'd said yes. In Pory a blogger or YouTuber creates their own account from the sign-up page and lands in the Affiliate role, then adds their channel and audience for review. Nobody on the team sets up logins one at a time.
Vetting creators used to mean a spreadsheet of links and a gut feeling nobody wrote down. The partnerships manager opens an application, checks the channel, platform and audience size, and approves or rejects it with a reason on the record. Rejected creators get a real answer, and the next person on the team can see why.
"When's my payout?" used to be the most common email in the affiliate inbox, month after month. In Pory each affiliate signs in and sees only their own payouts: the date, referred orders, commission and status, from pending to paid. Finance marks a payout paid once it's sent, and the question answers itself.
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 affiliates, flat price.