Directory
A nonprofit member portal is where members find each other in a directory and read their benefits and updates, the coordinator tracks each member's dues status, and renewals come with a reminder.
Pattern: DirectoryDescribe it to Pory
“We're a wetlands charity with 600 members. We want a member directory, benefits and updates pages, dues status for each member, and renewal reminders.”
Directory
In plain English
A nonprofit member portal is where members find each other in a directory and read their benefits and updates, the coordinator tracks each member's dues status, and renewals come with a reminder. It follows the Directory pattern: who belongs, their profiles and sign-ups. Pory generates it from a plain-English description, with a login for each role (member and membership coordinator) that shows only what that role should see, and flat pricing with unlimited members.
What it does
Members who met at a work party had no way to find each other again except asking the office, which couldn't hand out details anyway. In Pory signed-in members browse a directory of names, membership types and home towns, with dues kept off it entirely. The office stops working as a switchboard.
Dues were cross-checked between bank statements and a spreadsheet that was always a month behind. In Pory each membership has its own dues record — renewal date, amount and status — which only the member and the coordinator can see. Finding who has lapsed takes a filter, not a Sunday afternoon with a highlighter.
Updates went out as an emailed PDF newsletter, opened mostly by the people who wrote it. In Pory the coordinator keeps benefits and updates on pages inside the portal: guided walks, the photography hide, the latest survey count. Members see what their membership gets them without digging for last spring's email.
Renewals relied on the coordinator remembering to write to each member in the right month, which slipped every spring. In Pory each dues record has a renewal date, and the member gets a reminder in the portal and by email ahead of it. Fewer memberships lapse just because nobody mentioned it.
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 members, flat price.