My units
Units
| Unit | Owner | Occupancy | Tenant | Monthly rent | |
|---|---|---|---|---|---|
| 12 Alder St, Unit 3 | Chioma Eze | Let | J. Moretti | 2300 | |
| 12 Alder St, Unit 5 | Chioma Eze | Notice given | R. Afolabi | 2150 | |
| 40 Quarry Rd | Chioma Eze | Under repair | — | 2600 |
Showing 1–3 of 3
A property owner portal is where a property manager shares each owner's units, monthly statements and maintenance history with that owner and nobody else. Owners see the rent collected and spend recorded on each of their units instead of waiting for an emailed PDF.
Pattern: TrackingDescribe it to Pory
“We manage about 80 rental units for 30 private owners. Each owner should sign in and see only their units, their monthly statements, rent collected and spend per unit, and the maintenance done on each.”
My units
| Unit | Owner | Occupancy | Tenant | Monthly rent | |
|---|---|---|---|---|---|
| 12 Alder St, Unit 3 | Chioma Eze | Let | J. Moretti | 2300 | |
| 12 Alder St, Unit 5 | Chioma Eze | Notice given | R. Afolabi | 2150 | |
| 40 Quarry Rd | Chioma Eze | Under repair | — | 2600 |
Showing 1–3 of 3
In plain English
A property owner portal is where a property manager shares each owner's units, monthly statements and maintenance history with that owner and nobody else. Owners see the rent collected and spend recorded on each of their units instead of waiting for an emailed PDF. It follows the Tracking pattern: a person's or asset's history, built up over time. Pory generates it from a plain-English description, with a login for each role (owner and property manager) that shows only what that role should see, and flat pricing with unlimited owners.
What it does
Owners got a monthly email with a spreadsheet attached, and one wrong recipient put another owner's tenants and rent on show. Each owner signs in to a list of only the units they own (occupancy, tenant, rent and lease end) and the property manager keeps it current. Nobody triple-checks the To: line before hitting send.
Owners waited for month end to learn whether a unit was let and what the plumber had cost. The manager records each unit's rent collected and spend for the month on the unit itself, and the Home page counts how many units are let and how many sit vacant. Owners read the figures on their own units instead of phoning the office for them.
Statements went out as PDF attachments that owners' accountants asked for again every tax time. The manager uploads each month's statement against the unit, and each owner sees their own statements with the issue date and whether the next one is still being prepared. Tax time becomes a few clicks, not a search through two years of email.
Owners asked what had been spent on a unit and got a string of forwarded invoices back. Each maintenance job is filed against its unit with the date, the contractor, the cost and whether it's done. An owner opens 40 Quarry Rd and sees the ceiling repair and the repaint together, without asking the manager to dig them out.
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 owners, flat price.