Feature request board portal

A feature request board portal is where customers submit product ideas and follow what happens to each one, the product team triages requests through to planned, and a public roadmap page lets anyone see what's coming and suggest more.

Pattern: Requests

Describe it to Pory

“Our customers send feature requests. We want them to submit ideas in one place and see what happened to theirs, with the product team triaging them onto a public roadmap.”

Viewing as

My requests

My requests

Powered by Pory

In plain English

What is a feature request board portal?

A feature request board portal is where customers submit product ideas and follow what happens to each one, the product team triages requests through to planned, and a public roadmap page lets anyone see what's coming and suggest more. 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 (customer and product team) that shows only what that role should see, and flat pricing with unlimited customers.

What it does

01

Customers post an idea once, with the reason they need it

Feature requests were scattered across support tickets, sales call notes and a Slack channel called #ideas-maybe. In Pory a customer names the idea, picks the area of the product, explains what it would let them do and attaches a mock-up if they have one. The product team reads the request in the customer's own words, not a paraphrase from a call three weeks ago.

Forms to submit a recordDone by: Customer
02

The product team drags ideas from new to planned or declined

Triage used to be a spreadsheet session where half the rows were duplicates and nobody remembered who had asked. In Pory each request is a card in New, Under review, Planned, Shipped or Declined, and the product team moves it along as decisions get made. The requester's name stays on the card, so someone always knows who to tell.

Board by statusDone by: Product team
03

A public roadmap page anyone can open, no login required

The roadmap was a slide shown on sales calls and emailed to whoever asked, already out of date by the time it landed. In Pory the roadmap page is public: prospects and customers open it without an account and see every idea marked Planned or Shipped, straight from the same records the team triages. Sales stops attaching "latest roadmap" slides to follow-up emails.

Public pages & formsDone by: Product team
04

Customers check their own idea's status instead of asking sales

Customers who asked for a feature never heard back unless they chased their account manager, who then chased product. In Pory each customer sees their own requests with a progress bar from New through Under review to Planned and Shipped. When dark mode ships, the person who asked for it can see that it did.

Status tracker for the submitterDone by: Customer

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 feature request board portal, live today.

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