Tenant portal

A tenant portal is where renters report repairs and follow each one to fixed, and see whether each month's rent is marked received, due or late. The property manager works the requests and keeps rent status current, and each tenant sees only their own.

Pattern: Client hubs

Describe it to Pory

“We manage a 36-unit apartment building. Tenants should report repairs and follow them, and see their rent status each month, while our property manager handles the requests.”

Viewing as

My repair requests

My repair requests

Powered by Pory

In plain English

What is a tenant portal?

A tenant portal is where renters report repairs and follow each one to fixed, and see whether each month's rent is marked received, due or late. The property manager works the requests and keeps rent status current, and each tenant sees only their own. It follows the Client hubs pattern: one shared space per client: deliverables, documents, milestones. Pory generates it from a plain-English description, with a login for each role (tenant and property manager) that shows only what that role should see, and flat pricing with unlimited tenants.

What it does

01

Tenants report a leak with a photo and the room it's in

Repairs used to arrive as voicemails, texts to the manager's mobile and notes slid under the office door, and half forgot the unit number. A tenant picks the room, describes the problem, attaches a photo and says when someone can come in. The request lands with their name and unit on it, so nobody plays phone tag to find the flat with the leak.

Forms to submit a recordDone by: Tenant
02

Every repair shows how far along it is, from reported to fixed

Tenants chased repairs by ringing the office to ask "any news on the hot water?". Each request they've filed shows as a progress bar (Reported, Booked, In progress, Fixed) and the manager moves it along as the plumber books in. Tenants check their own page instead of the office phone, and the manager gets a quieter Monday.

Status tracker for the submitterDone by: Tenant
03

Each tenant sees which months are received, due or late

Tenants emailed the office to ask whether this month's rent had landed, and the answer lived in the manager's spreadsheet. The manager marks each month received, due or late on the tenant's rent row, and each tenant sees their own months and no one else's. The first of the month stops bringing a pile of "did you get it?" emails.

Tables to manage recordsDone by: Tenant

The parts every portal is built from

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

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Record pop-up & linked records

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.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the rows a viewer is allowed to read.

Control

Role & row access

Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

On purpose

Four things Pory won’t do

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.

Take payments

Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.

Book time slots

Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.

Host the conversation

No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.

Plan routes

Pory keeps the service record, not the map.

Frequently asked questions

Your tenant portal, live today.

Describe it in a sentence and send the invite. Unlimited tenants, flat price.