My requests
A mutual-aid fund portal is where neighbours request support privately, a committee approves or declines each request with a reason, and the treasurer records every disbursement against the request it answers.
Pattern: RequestsDescribe it to Pory
“We run a neighbourhood mutual-aid fund. People request support, our committee reviews and decides, and the treasurer records each disbursement.”
My requests
In plain English
A mutual-aid fund portal is where neighbours request support privately, a committee approves or declines each request with a reason, and the treasurer records every disbursement against the request it answers. 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 (neighbour, committee and treasurer) that shows only what that role should see, and flat pricing with unlimited neighbours.
What it does
Asking for help meant posting in a group chat half the neighbourhood could read, or catching an organiser at the food share. In Pory a neighbour files a request with what it's for, how much and by when, then sees it move from Submitted to a decision. Nobody has to explain their rent to three different volunteers.
Decisions happened in late-night voice notes, and the person asking heard back whenever someone remembered to tell them. In Pory the committee opens each request, reads the need, amount and date, and approves or declines it with a short note kept on the record. Nobody has to reconstruct from memory why the car repair was turned down.
Knowing what had actually gone out meant checking a banking app against a notebook the treasurer kept in her bag. In Pory each disbursement is its own record, linked to the request it answers, and the Home page counts how many are scheduled and how many are sent. Committee meetings start from the count, not a search through old messages.
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 neighbours, flat price.