Intake forms land on the right record, clinicians keep their notes private, and each patient or family sees only what's theirs.
Describe it to Pory
“A clinic portal where patients fill in intake forms and upload insurance documents, and only clinicians see the medical history.”
Pets
| Name | Species | Breed | Owner | Age | |
|---|---|---|---|---|---|
| Biscuit | Dog | Beagle | Tariq Hassan | 4 yrs | |
| Miso | Cat | Domestic shorthair | Tariq Hassan | 2 yrs | |
| Juniper | Rabbit | Netherland dwarf | Elena Popescu | 1 yr | |
| Rocket | Dog | Border collie | Ben Adler | 7 yrs | |
| Pepper | Bird | Cockatiel | Keiko Sato | 3 yrs | |
| Olive | Cat | Ragdoll | Marisol Vega | 10 yrs |
Showing 1–6 of 6
A veterinary clinic portal, one of the 9 portals below. See how it works
In plain English
A patient portal gives each patient or client a secure login to fill in forms, upload documents and see their own records, while clinicians keep notes the patient never sees. Pory generates one from a plain-English description, with role-based access set up for you and flat pricing that never charges per patient.
Each one comes with its own demo and a walk-through of the jobs it does.
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 who it's for and what each person needs, then send the invite. Unlimited members, flat price.
