Beta program portal
A beta program portal is where people sign up to test a product, the beta team approves or declines each applicant, approved testers send feedback on each build, and the team shares release notes as files.
Pattern: RequestsDescribe it to Pory
“We're running a beta for our podcast app. People should sign up, we approve who gets in, testers send feedback on each build, and we share release notes with them.”
Join Wavelength Beta
Create your account as a beta tester. We'll email you a link to finish.
In plain English
What is a beta program portal?
A beta program portal is where people sign up to test a product, the beta team approves or declines each applicant, approved testers send feedback on each build, and the team shares release notes as files. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (beta tester and beta team) that shows only what that role should see, and flat pricing with unlimited testers.
What it does
Testers join on their own from a sign-up page, no invite list
Beta sign-ups used to be a form, a spreadsheet of email addresses and a batch of invites sent by hand every Friday. In Pory people create their own account from the sign-up page and land in the Beta tester role, with a tester's view of the portal from their first visit. The team stops copying email addresses between tabs.
The beta team approves applicants by device and reason, one click each
Choosing testers meant scrolling a spreadsheet of sign-ups and hoping the Android users weren't all left out. In Pory each applicant is a card showing their device, with their reason for wanting in on the record, and the team approves or declines them right there. The waitlist is a column on the board, not a tab nobody opens.
Testers file feedback against the build they were using
Beta feedback came in through app store reviews, DMs and a Discord channel nobody could search. In Pory a tester picks the build, marks it a bug, an idea or praise, describes it and attaches a screenshot. They can see whether the team has read it or planned it, which keeps testers testing.
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, in its detail view, 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.
Detail view with related items
Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the records a viewer is allowed to see.
Control
Who sees which records
Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up 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.
Frequently asked questions
More customer support portals
All customer support portalsYour beta program portal, live today.
Describe it in a sentence and send the invite. Unlimited testers, flat price.