Directory
A faith community portal is where members find each other and their small groups, group leaders see their own group, everyone shares one events calendar, and members ask the pastoral team for care.
Pattern: DirectoryDescribe it to Pory
“Our church needs a member directory with small groups, a page for each group leader to see their people, an events calendar, and a way to ask for care.”
Directory
In plain English
A faith community portal is where members find each other and their small groups, group leaders see their own group, everyone shares one events calendar, and members ask the pastoral team for care. 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, group leader and pastoral team) that shows only what that role should see, and flat pricing with unlimited members.
What it does
New members spent months learning names, and the printed directory was always a few house moves out of date. In Pory signed-in members browse a directory with each person's photo and small group, from Young families to the choir. The welcome team stops photocopying a list that changes every month.
Leaders kept their group list on their phone, while the office kept a different one, and neither agreed after a busy September. In Pory a leader signs in and sees the members of their own group, with the date each one joined, and nobody else's. The Tuesday list and the office list stop contradicting each other.
The Sunday notice sheet did its best, but anything past the weekend lived in the pastor's diary. In Pory the office puts services, group nights and community events on a calendar members can open any day of the week, each with its time and place. Fewer people turn up at the church hall on the wrong Thursday.
Care needs reached the pastoral team by chance: a word after the service, a message to whoever happened to answer. In Pory a member files a care request with what's needed and by when, then sees when it's in hand. Requests go to the pastoral team only, not round the whole prayer chain.
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.