A mutual-aid fund portal is where neighbors 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 neighborhood mutual-aid fund. People request support, our committee reviews and decides, and the treasurer records each disbursement.”
My requests
| Your rent account number, so we can pay your landlord directly | Oct 19, 2026 | Asked | |
| Which day does the new job start? | Oct 1, 2026 | Answered |
Showing 1–2 of 2
| Monthly bus pass | 60 | Oct 3, 2026 | Bank transfer | Sent | |
| School shoes, two pairs | 70 | Sep 17, 2026 | Bank transfer | Sent |
Showing 1–2 of 2
In plain English
Pory gives every neighbor, committee and treasurer a sign-in of their own. Each neighbor sees only their own requests. It covers requests & disbursements. Requests, disbursements, questions, fund dates and who reads your request live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Asking for help meant posting in a group chat half the neighborhood could read, or catching an organizer at the food share. In Pory a neighbor 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.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own requests.
Sees every request in the portal.
Sees every request in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Live figures over the records a viewer is allowed to see.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited neighbors.
